AGILE TESTING Artem Bykovets (ScrumMaster, IT/QA and Agile coach, founder at StartIT)
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
AGILE TESTING
Artem Bykovets (ScrumMaster, IT/QA and Agile coach, founder at
StartIT)
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
TRADITIONAL VS. AGILE TESTING
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
THANK YOU! QUESTIONS?
CONTACTS:ua.linkedin.com/in/abykovetsSkype: arthar4egmail: [email protected]
www.start-it.com.uahttps://www.facebook.com/QASTARTITOffice: 063 742 50 52
Related Documents
