Agile Testing
In agile teams testing is continuous and shared. Testers work alongside developers every day, not at the end.
On this page · 5 min · Advanced
On this page
- Learning objectives
- Explanation
- Code example
- Step by step
- Real-world use
- Common mistakes
- Best practices
- Remember this
- Practice exercise
- Mini quiz
- Related topics
- My notes
- Reading time
- 5 min
- Difficulty
- Advanced
- Updated
- Oct 29, 2026
Related tutorials
Learning objectives#
- Describe the tester’s role in Scrum
- Test user stories with acceptance criteria
- Use the agile testing quadrants
- Contribute to the definition of done
Explanation#
Testers join backlog refinement to clarify stories and write acceptance criteria, often as Given/When/Then examples.
Stories are tested within the sprint; a story is not done until it is tested and meets the definition of done.
Agile testing quadrants: technology-facing tests supporting the team (unit), business-facing supporting (story tests), business-facing critiquing (exploratory, UAT) and technology-facing critiquing (performance, security).
Code example: User story with acceptance criteria#
Story: As a customer, I want to save items to a wishlist so I can buy them later.
Acceptance criteria
Given I am logged in
When I click "Save to wishlist" on a product
Then the product appears on my Wishlist page
Given the product is already in my wishlist
When I click "Save to wishlist" again
Then I see "Already in your wishlist" and no duplicate is added
Given I am not logged in
When I click "Save to wishlist"
Then I am asked to sign in and returned to the product afterwards
Definition of done: code reviewed · unit tests · criteria tested · regression green · deployed to staging
Clear examples agreed before coding become the tests at the end of the sprint.
This example is illustrative. Copy or download it and run it in your own environment; the expected output is shown above.
Step-by-step explanation#
- Refine the story together and add examples.
- Developers build against the criteria.
- Testers test each criterion as soon as it is ready.
- The story meets the definition of done before the sprint ends.
Real-world use case#
A Scrum team ships every two weeks with testing completed within each sprint.
Common mistakes#
If testing starts on the last day, stories spill over. Test continuously.
Use concrete examples so everyone shares the same understanding.
Best practices#
- Testers in refinement
- Given/When/Then examples
- Test stories as soon as they are ready
- Automate regression to keep up with sprints
Remember this#
Testing is continuous in agile.
Acceptance criteria = examples = tests.
Not tested = not done.
Practice exercise#
Your task: Write one Given/When/Then criterion for “Remove item from cart”.
Show solution
Given my cart contains a Laptop and a Mouse
When I remove the Mouse
Then the cart shows only the Laptop and the total updates to ₹55,000
Mini quiz#
When should testers get involved in an agile user story?
Want more? Practise all Manual Testing MCQs · Manual Testing interview questions
My notes#
Saved in this browser.