Agile Testing and Scrum for Testers

Agile Testing Introduction

In Agile, testing happens inside every sprint, not after development. Testers join planning, write cases from user stories, automate continuously and demo working software every 1-2 weeks.

Scrum for Testers

• Planning - question stories, agree acceptance criteria, estimate testing effort.
• Daily standup - report blockers (waiting on build, data, environment).
• Review/Retro - demo tested stories, improve the process.

User Stories and Acceptance Criteria

As a shopper I want to apply a coupon
so that I save money at checkout.
AC: valid coupon reduces total; invalid shows error;
    one coupon per order; works with COD.

Definition of Done

A story is done only when code is reviewed, unit tested, QA passed, automated, documented and deployed to staging. No hidden leftover work.

QA in Agile and Continuous Testing

• Shift-left - test stories before coding starts.
• Continuous testing - every commit triggers unit, API and smoke suites in CI.
• QA automation in CI/CD - regression runs on Jenkins/GitHub Actions; failures block the merge.

Key Points

• Testers are sprint members, not a phase after it.
• Acceptance criteria are the test contract.
• Done means releasable, not just coded.