Agile testing
Download as PPS, PDF0 likes590 views
The document discusses the differences between traditional testing methods and agile testing, emphasizing the iterative and incremental nature of agile practices. It critiques the illusion of control in waterfall SDLC models and highlights the importance of repeatable quality in true agile teams. Additionally, it addresses the need for testers to be involved early and continuously in the development process to ensure that features are tested as they are completed.
Agile testing
- 1. AgileТестировщик в :среде отличие реалий от книжной теории Artem bykovets (ScrumMaster, it/qa agile coach, founder at start-it)
- 3. In result • post-development testing phases were expected to boost quality after code was complete. We had the illusion of control • Traditional teams are focused on making sure all the specified requirements are delivered in the final product. If everything isn’t ready by the original target release date, the release is usually postponed. • Sometimes testers must seat and wait for some work to do
- 5. Traditional vs. Agile Testing
- 6. Agile Testing • While some teams do seem to use the “agile” buzzword to justify simply doing whatever they want, true agile teams are all about repeatable quality as well as efficiency • Agile is iterative and incremental. This means that the testers test each increment of coding as soon as it is finished • Programmers never get ahead of the testers, because a story is not “done” until it has been tested
- 9. Contacts: • www.start-it.com.ua • Mail: A.bykovets@start-it.com.ua • https://www.facebook.com/QAStartIT • ua.linkedin.com/in/abykovets • Skype: arthar4eg • Office: 044 33 77 427
- 10. Contacts: • www.start-it.com.ua • Mail: A.bykovets@start-it.com.ua • https://www.facebook.com/QAStartIT • ua.linkedin.com/in/abykovets • Skype: arthar4eg • Office: 044 33 77 427