Agile Testing

Agile testing was fairly new because of prevalent of waterfall model. The short deployment time of Agile will often means a reliance on automated testing. However, these automated testing often relies on known scenarios and limited scope. Thus, you will need to relied on past experiences to conduct testing for Agile.

What to Expect

Agile have shorter time to deployment than waterfall. Thus, coding and testing strategies must vary from that of waterfall model.

  1. Codes must allow graceful exit of exception scenarios i.e no crashes.
  2. Codes must be scalable for additional test scenarios.
  3. Failed test are often due to additional scope and and will be updated into backlog. Thus, they are not showstopper to deployment.
  4. User Acceptance Testing (UAT) are optional because of close collaboration with users.
Mindset Change

Users must stop their negative mindset of saying “it’s an IT project”. Application of Agile testing requires deep mindset changes. You cannot continue to apply the traditional approach of UAT. Instead, users must collaborate closely and be committed with the development team. This way, Agile can be realised in quicker deployment without the need for time consuming UAT.

2 thoughts on “Agile Testing

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s