QA in an Agile team and test tools
Sprints, user stories and acceptance criteria, Jira workflows, and how testers work day to day.
Most IT park companies work in Agile teams using Scrum: work is split into short sprints (often two weeks), planned from a backlog of user stories.
The tester's role in a sprint
- Sprint planning / refinement — question stories and help write clear acceptance criteria.
- During the sprint — write test cases while developers code, test stories as they finish, log and retest bugs.
- Daily stand-up — share what you tested, what's blocked, and risks.
- Sprint review / demo — confirm accepted stories meet the criteria.
- Retrospective — suggest process improvements.
Acceptance criteria
Often written as Given / When / Then, they become direct test cases.
Common tools
Jira (stories and bugs), test management tools for test cases, Postman for APIs, Selenium or similar for UI automation, and Git plus a CI server to run automated tests on every build.
Example
Practise on any app you useUser story: As a shopper, I want to save items to a wishlist so that I can buy them later.
Acceptance criteria: Given I am logged in When I tap the heart icon on a product Then the product appears in My Wishlist And the heart icon turns filled
Given I am logged out When I tap the heart icon Then I am asked to log in first
Test cases derived: TC_WL_01 (add), TC_WL_02 (logged out), TC_WL_03 (remove), TC_WL_04 (wishlist persists after re-login)
What to notice
• Each Given/When/Then maps directly to a test case.
• The tester added TC_WL_03 and 04 — cases the story implied but didn't spell out. Spotting these gaps is where QA adds value.
Apps, IDs and data are fictional examples written for practice.
Key points
- Testers join planning, not just testing.
- Acceptance criteria (Given/When/Then) become test cases.
- Test continuously during the sprint.
- Know Jira, Postman, Selenium and Git basics.
Quick check
What are acceptance criteria used for?
Acceptance criteria state the conditions a story must meet, which testers turn into test cases.
Practice task
Write a user story and three Given/When/Then acceptance criteria for 'reorder a previous order' in a grocery app, then derive four test cases.
Interview corner
What do you do if a story has no acceptance criteria?
Raise it in refinement, propose criteria based on your understanding, and confirm them with the product owner before testing.
How do you decide what to test when time is short?
Use risk-based testing: prioritise critical user flows, recently changed areas and features with past defects, and communicate what was not covered.
Original lesson written by the InfoparkDaily team · © 2026 InfoparkDaily · Free to learn — no paid course or subscription.