Agile Testing 1/2

Agile testing is executed in a very different way from the traditional norm. It basically consists of a continuous process throughout the software development life cycle as the testing provides information about the new software’s performance as well as the functionality. As a result there is no time for detailed testing of the software at a later stage let alone doing the necessary corrections, since it is an iterative process. Therefore the first sprint is developed and tested. Then the second is developed and tested in isolation, before being integration tested with the first sprint. This goes on and on till the software has been completely developed.

Challenges in Agile Testing

• Due to the tight timelines, there is hardly any time for detailed test planning.
• There are too many changes in the software requirements and development which conflict with the test planning
• The testing phase is not specified. That is, it is not clear when tests start and end.
• Since testing starts when the first iteration is complete, judging at that stage whether it will lead to working software is difficult.

Involvement of Testers at Every Stage

In agile testing, a tester is a utility person, whose skills are used throughout the process of software development.

Whilst going through the creating a project plan phase, they are utilised to clarify the project management requirements from the customer as well as suggest alternatives. When requirements are well understood at the planning stage, it is easier to later accurately estimate project costs as well as deliver within the given time frames.

During the development stage, agile testers will work with the developers to write the code in such a way that it will be easier to test later on. Hence time is saved again.

By the time the testing stage starts, the tester's are completely aware of the user requirements and what the system is expected to do. As such they can do their job well, even without an exhaustive requirement specification or business requirements documentation.

The Phases of Agile Testing

1.0 Unit Testing

The developers do the unit testing of their code. Think of this as being an initial test to see whether the code works at a high level. These tests should be automated as far as possible to reduce the testing time.

2.0 Integration Testing

Integration testing and system testing start together. As soon as the second sprint is over, the system and integration testing of that sprint, together with the other ones start.

3.0 Regression Testing

After each period of integration testing there is a short cycle of regression testing. As the development is automated test driven, the system should be working well at this stage and hence there would be no need for a long period of regression testing.

Please click here for the remainder of the Phases of Agile Testing as well as the Key Points and Values of Agile Testing.