What does your task board say about your team? Many teams have a separate testing column. This indicates that we are still doing hand-offs from development to testing and that testing is an afterthought. Testing is not a phase that happens at the end of a project and it’s not a phase that happens at the end of a sprint or at the end of a story. Testing is an ongoing activity that happens throughout and there is no distinction between programming or coding and testing. It’s just quality development. It’s about building quality-in instead of checking for quality later. So that’s why testing starts from day one.
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