Test Preparation - Agile approach

1. What? Why? When? Who? Where?
Internal Grooming
· Walkthrough the stories, clarify
functional understanding
Generally happens soon after the
Grooming or Planning meeting
All testing team members
EPIC specific Mind Maps (planning to
store them under Jira EPIC)
· Re-assess story point estimation
· Brings functional awareness to
all testers (even the ones that are not
individually worked up on)
User Story Understanding
Primarily to raise all new/open queries
with PO
1st Step of Test Preparation activity, as
soon as the story is picked up
Individual Testers to whom it is
assigned
Documented under Jira story
comments section
Test Scenarios Identification
· Serves as a Heads-up to
Developer on understood scope of
testing 2nd Step of Test Preparation activity
Individual Testers to whom it is
assigned
Under Test preparation subtask’s
description
· PO can confirm if we have the
right understanding
Test Case Creation
To provide a detailed scope of test
cases that are to be executed on the
functionality. Generally captures all
below:
3rd Step of Test Preparation activity
Individual Testers to whom it is
assigned
Zephyr
· Title
· Description
· Test Steps & Expected Result
· Respective Story ID
Test Case Review
To identify & alter any understanding
gaps 4th Step of Test Preparation activity
Peer/Lead (and/or) respective
Developer
In-formal communication or as
comments under Test Preparation
activity
Test Case Modification To keep the test cases right As soon as Review meeting is over
Individual Testers to whom it is
assigned Zephyr
Test Data Preparation Readiness for Test Execution
Post Completion of Test Case
Writing/Update
Individual Testers to whom it is
assigned QE Environment
Technical dependency exploration
&
Test Environment Setup
Readiness and avoid any delay from
dependent teams (DevOps, Database,
etc)
Post Completion of Test Data
Preparation
Individual Testers to whom it is
assigned QE Environment