Agile Testing 2/2

The Phases of Agile Testing Cont

Please click here for the beginning of the Phases of Agile Testing

4.0 Stability Testing

A really large project which goes on for several months will include numerous sprints. Thus, just before the final build of software is released to go into live or production, a short period of stability testing is usually necessary. This checks that the software works as intended and that the system is isn't going to crash the minute it goes live.

The Key Points and Values of Agile Testing

1.0 Delivering software Which Actually Works as Intended is More Important Than the Documentation Produced

Your emphasis needs to be more on testing that the software actually works, rather than producing reams of paperwork.. The documentation detailed should only as much as is required to get the job done. It is then up to the test team to carefully decide how to test each sprint of the software as well as the integrated builds.

2.0 Interaction with the Team is More Important than Testing Tools and Processes

Communication between the testers, developers and users will facilitate the testing process much more than spending an inordinate amount of time determining which testing tools and processes to use. This is also particularly important since the agile testing time is so short on a project, therefore the testers need to understand what the functionality of the software will be well ahead of time in order to understand how to most effectively test it. As a result testers on such a project need to be heavily involved whilst the agile requirements are determined.

3.0 Customer Participation is More Important than Negotiations Over the Contract

Contract negotiations tend to take too much time to resolve. Hence it is better to work in collaboration with the customer so that the testers do not have to play the role of devil’s advocate in deciding how functionality should work.

4.0 Flexibility to Change the Functionality is More Important than Resisting Changing the Plan

Agile testing believes in flexibility to change scope and functionality. As soon as the requirements change, the test plan and even the project plan also has to change or else it will be of no use. Therefore both need to be kept high level to ensure they can be easily modified and maintained in the ever changing environment which agile creates.

Agile Testing - Tip

Agile testing should be automated as far as possible because manual testing consumes a great deal of time. Since there is always a definite possibility that the project will get delayed or might uncover bugs at a late stage, the sooner these are found the better to ensure they can be dealt with prior to launch.