Agile Testing

This presentation was used during my talk about Agile Testing at Agile Tour Yerevan 2015

Transcript

1. Agile  Tes)ng Sargis  Sargsyan                                                      Automa)on  QA  Engineer  at
2. One Slide Agile Overview Agile …. • is an umbrella term coined in 2001 at “Snowbird” meeting to describe a variety of methods including XP and Scram • has its roots in iterative development • emphasizes collaborative, integrated teams; frequent deliveries; and the ability to adapt to changing business needs
3. Nine Principles
4. Testing  Moves  the  Project  Forward … to providing information, feedback, and visibility …from being the last line of defense Shifting Focus
5. Testing  is  NOT  a  Phase Phased Develop Test Integrated Develop  &  Test
6. Everybody  Tests…   Not just the designated testers
7. Reduce  Feedback  Latency Long gaps between implementing and testing increase risk and waste. Agile teams test early and often.
8. Tests  Represent  Expectations The Challenge is to find the balance point between testing for implicit expectations and making up requirements as yo go.
9. Bugs  Don’t  Hang  Around Buggy Software is harder to test, harder to modify, and slows everything down. Keep the code clean. Fix bugs fast
10. Reduce  Test  Documentation  Overhead
11. Tested  is  Part  of  “Done” “Done” means implemented and tested. If it isn’t tested, you don’t know that the implementation matches expectations.
12. Form  Test  Last  to  Test  Driven
13. Six Concrete Practices
14. Automated  Unit/Integration  Tests are code facing, written by programmers in support of the programming effort are (usually) created using one of the xUnit frameworks Express expectations of internal behavior of the code Isolate the element(s) under test Execute quickly Are executed often, with every change
15. Test  Driven  Development  (TDD)
16. Automated  System-­‐Level  Regression  Tests Are business-facing, written by various members of the team in collaboration Express expectations about externally verifiable behavior Are (mostly) end to end Represent executable requirements Execute as part of the continuous integration process
17. Acceptance  Test  Driven  Development  (ATDD) ATDD cycle model by Jim Shore with changes suggested by Grigori Melnick, Brian Mericl and Elisabeth Hendrickson
18. Exploratory  Testing Simultaneously…. …learning about the software …designing tests …executing tests using feedback from the last test to inform the next
19. Effective  Testing  on  Agile  Projects… …ultimately becomes a whole team effort integrated throughout the development cycle
20. Thank you.