Stop 04 · SDLC, Agile & Testing MethodologiesTopics · 3/9

Testing in Sprints

In short

Two weeks sounds like plenty, until every story lands on day nine. Testing well in a sprint is about timing, small stories and not leaving everything to the end.

Fitting the full test cycle (design, execute, report, retest) within a short sprint timeframe — requires efficient test case design and often relies on automation to keep pace with rapid development cycles.

The purple blob calmly studies at a neat desk with a wall calendar beside it.

Think of it like this

Two weeks before semester exams

Students who revise a bit every day sleep before the exam. Students who leave six subjects for the last night don't. A sprint is the same: test each story as it arrives, not all on the final day.

Watch it happen

Testing through a two-week sprint

Planning

Write tests

Test stories

Regression

Review

1/5Day 1: the team picks stories. QA includes testing effort in each estimate.

The big ideas

What you need to know

Small stories help

Small stories finish early and can be tested early. Big ones tend to arrive on the last day.

Count testing in estimates

A story isn't done when coding ends. Testing and fixes are part of its size.

Automate as you go

Add automated checks for stable stories each sprint so regression doesn't grow into a monster.

Save yourself the pain

Common mistakes

Oops

Quietly accepting that all stories arrive on the last day.

Do this instead

Raise it in retro. Suggest smaller stories or a mid-sprint 'code complete' target.

Oops

Carrying untested stories into the next sprint as 'done'.

Do this instead

If it isn't tested, it isn't done. Be honest in the review.

Your mission

Plan your sprint testing

~20 min

Quick check

Most stories in your sprint reach QA on day 9 of 10. What's the best long-term fix?

Go deeper

1Draft a testing plan that fits within a 2-week sprint for a hypothetical feature.
2Learn why automation becomes increasingly necessary as sprint length shortens.
3Understand why testing debt (untested features) can silently accumulate if sprint testing falls behind.