To summarize, here are the top 8 things to consider when developing your Agile testing strategy to enable you to continuously deliver a quality working product increment at the end of every Sprint
- Testing in not a phase
2. Testing is everyone’s responsibility
3. Testing starts on day 1
4. Do automate all scripted tests
5. Developers are the one’s doing most of the automation
6. Do use executable documentation
7. Do not automate functional testing via the UI
8. Save most manual testing for usability and exploratory testing
Also check out the entire Agile Testing series:
- 4 Typical Transitions Teams Go Through When They First Start Adopting Scrum
- The Most Common Misunderstanding of Agile Software Development
- What are the Different Types of Tests?
- What is The Agile Testing Quadrant?
- Which Tests Should We Automate?
- How Many Tests Are Enough?
- What is The Testing Pyramid?
- When Do We Start Testing in Scrum?
- Who Is Responsible for Testing in Scrum?
- What is Test Driven Development (TDD)?
- Why You Shouldn’t Do Functional Testing From the UI?
- What are Executable Specifications or Specifications by Example?
- What is Acceptance Test Driven Development (ATTD)?
- Testing Green Field Applications vs. Legacy Applications
- What is Exploratory Testing?
- Top 8 Things to Consider for Your Agile Testing Strategy
- Agile Testing – Testing from Day 1 Presentation
