Testing In The Agile System places more emphasis on how tests are done as what gets tested is the same as other QA programs. Business / The Guardian Podcast / Uncategorized

In the Agile methodology there are mostly the same types of tests as are used in other quality assurance programs. What gets tested is the same. It is the “how” that is different. How things are tested using the Agile methodology is the biggest difference. There is lots of testing. People who use software enabled devices and software may not realize how many tests there are. Most testers aim for testing 80%, but in Agile its well over 90%. This is especially the case in regulated industries or anything that has direct customer feedback. So anything that has a URI, anything that has to do with money, anything that has to do with healthcare, anything that is security data or hs personal information to the other thing we emphasize in addition to automated testing with Agile.

The other type of testing with Agile is iterative testing. No one tests A-E, instead we start with user story A which leads to B and we test A to B. A is automated at this point. Then test C. Both A and B are automated so this gets us from A-C. The we manually test D and so on so each user story builds on the last test until all are automated.

Testing In The Agile System places more emphasis on how tests are done as what gets tested is the same as other QA programs.

Testing In The Agile System places more emphasis on how tests are done as what gets tested is the same as other QA programs.

The Team Approach For Testing

Everyone on the team is responsible for testing. Knowing what is to be tested from the beginning helps. When we think of the two most important pieces of the user story, the description which tells you what has to be done and why and then we have the acceptance criteria. I can’t tell you how many really matureAagile organizations I worked with that’s all they have in their user story. They don’t have preconditions and assumptions, or business rules. If you’re really good at writing acceptance criteria already covers all those other areas tell you everything you need to know about the what for that user story. The whole team writes acceptance criteria. Everybody participates in the activity. Testing often takes longer than development, almost always. So what we’ll do is when the developers are getting too far ahead of testers, we will stop development and will have them go help the testers, , so it’s always a very synergistic relationship.


Leave a Reply

Your email address will not be published. Required fields are marked *