Entry and Exit Criteria for Each Phase
Entry and exit criteria are the quality gates that make the STLC a controlled, professional process rather than an ad-hoc checklist. They define when a phase can start (entry) and when it can be considered complete (exit). Without them, teams skip phases under time pressure, testing starts on unstable builds, and releases happen before quality is achieved.
Complete Entry/Exit Criteria Reference
- Phase 1 - Requirement Analysis: ENTRY: Approved requirements doc available, team staffed. EXIT: All requirements reviewed, ambiguities documented and answered, testability confirmed, RTM skeleton created
- Phase 2 - Test Planning: ENTRY: Phase 1 complete, project timeline confirmed, resources allocated. EXIT: Test Plan signed off by PM, QA Lead, and business stakeholders
- Phase 3 - Test Case Design: ENTRY: Signed Test Plan, approved requirements, RTM skeleton. EXIT: All test cases written, peer reviewed, and approved; RTM updated with test case IDs
- Phase 4 - Environment Setup: ENTRY: Test cases approved, build available for deployment. EXIT: Environment deployed, configured, and validated via smoke test; all team members have access
- Phase 5 - Test Execution: ENTRY: Environment validated, build deployed, test data prepared. EXIT: All planned tests executed (or deferral documented), critical/high defects resolved, Test Summary Report drafted
- Phase 6 - Test Closure: ENTRY: Test Execution complete, release decision made. EXIT: Test Summary Report signed off, RTM finalized, defect analysis done, lessons learned documented and presented
Negotiating Criteria Under Pressure
The most common challenge QA engineers face is stakeholders demanding release before exit criteria are met. Your response: 'These criteria were agreed upon in the Test Plan you signed at project start. Here are the open items that haven't met exit criteria: [list them with severity]. I recommend we document this as a known risk and get formal sign-off with the understanding that these issues may impact quality in production.' This approach is professional, non-confrontational, and creates documented accountability. Never silently compromise exit criteria - the quality problems that result will always be attributed to QA regardless of who made the decision.
Playwright rising fast - modern API, auto-waits, all browsers
Tip
Tip
Practice Entry and Exit Criteria for Each Phase in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
Practice Task
Note
Practice Task - (1) Write a working example of Entry and Exit Criteria for Each Phase from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Entry and Exit Criteria for Each Phase is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready qa engineering code.
Key Takeaways
- Entry and exit criteria are the quality gates that make the STLC a controlled, professional process rather than an ad-hoc checklist.
- Phase 1 - Requirement Analysis: ENTRY: Approved requirements doc available, team staffed. EXIT: All requirements reviewed, ambiguities documented and answered, testability confirmed, RTM skeleton created
- Phase 2 - Test Planning: ENTRY: Phase 1 complete, project timeline confirmed, resources allocated. EXIT: Test Plan signed off by PM, QA Lead, and business stakeholders
- Phase 3 - Test Case Design: ENTRY: Signed Test Plan, approved requirements, RTM skeleton. EXIT: All test cases written, peer reviewed, and approved; RTM updated with test case IDs