♻️Software Testing Life cycle
PHASE 1: REQUIREMENTS ANALYSIS
Entry Criteria
Project kicks off.
PMs/POs provide Epics and user stories
PMs/POs provide User flow (optional)(thru charts)
Project figma design is provided(optional)
Activities
Study functional and non-functional requirements. Understand the requirements in detail.
Study/create acceptance criteria using scenario and steps(
GIVEN... WHEN... THEN...)Identify testable requirements.
Story Mapping
Determine which gherkin steps syntax to be used for Acceptance criteria
Determine feasibility of test automation.
Exit Criteria
No more ambiguous or non-testable requirements/acceptance criteria.
Determined if test automation is feasible or not.
Note: This phase could only be possible for new projects and not for the ongoing projects.
PHASE 2: TEST PLANNING
Entry Criteria
Requirements Analysis was completed.
Activities
Test planning
Start writing test scenarios and test cases (*note: in an Agile development, test cases can be skipped)
Test Automation team should start preparing the tools and framework to be used.
Exit Criteria
Test Plan document
Test Scenario or test cases for Testing types
Test Automation tool and framework is ready.
PHASE 3: TEST DESIGN
Entry Criteria
Test Plan document is completed.
Activities
User Acceptance Testing/QA testing base from the test scenarios
Creating test automation from the stable versions/sprint/feature
Exit Criteria
The system passed from UAT
Test automation create from a sprint/version/feature
Last updated