ETVX – Is one of my favorite table which I have it in my test plan and implement, it will help you as quality gate for each phase and help understand to check what you should have before you start, what should you do to complete that phase, what should you validate before you say that you are done with the phase and the final deliverable/exit criteria.
I could not represent it in a table due to limitation with editor.
Envisioning Phase / Inception
(E)ntry Criteria
- Business Requirements available for review
(T)asks
- Review Business Requirements
- Log all discrepancies/ questions in Bug Tracker
- Provide High-level Test Estimates
(V)alidation
- All items in the bug tracker are closed with valid comments
- Business Requirements document is updated
(E)xit
- Signed-off Business Requirement Document
- High-level Test estimates are accepted by all stake holders
Design Phase
(E)ntry Criteria
- Signed-off Business Requirements
- Functional (FS) & Technical(TS) Specifications available for review
(T)asks
- Review FS & TS
- Raise questions/discrepancies in Bug Tracker to clarify if anything is ambiguous
- Provide detailed Test Estimates
- Review project plan and provide feedback to Program Manager
- Create master test plan & automation test plan and get it reviewed by appropriate stakeholders
- Generate traceability matrix
- Collaborate with all test teams to have complete coverage on integration areas
(V)alidation
- All items in the bug tracker are in closed state
- All review comments of master test plan and automation test plan are closed
(E)xit
- Signed-off TS
- Signed-off FS
- Detailed Test Estimates are accepted by all stake holders and incorporated appropriately in schedule
- Signed-off project plan
- Signed-off MTP
- Signed-off ATP
Build/Coding Phase
(E)ntry Criteria
- Signed-off TS
- Signed-off FS
- Signed-off MTP
- Signed-off ATP
- Availability of Test Environment details
(T)asks
- Write test cases to cover entire functionality and affected areas both from UI and DB perspective
- Get the test cases reviewed by appropriate stakeholders and get sign off
- Work with Operations /Support team to get test environments
- Validate SQL scripts against test cases in Dev/Unit Test environments
(V)alidation
- Test cases review
- Sanity check of test environments
- Sanity check of SQL scripts and UI automation scripts
(E)xit
- Signed-off test cases
- SQA environments are available for build deployment
- Validated SQL scripts against test cases
- Validated UI automation scripts
Stabilization/Testing Phase
(E)ntry Criteria
- Signed-off test cases
- Validated UI automation scripts
- Validated SQL scripts against test cases
- SQA environments are available for build deployment
(T)asks
- Execute test cases both manual and automation
- Publish daily report with test cases execution progress as well updated info on bugs
- Raise bugs in Bug Tracker appropriately
- Track bugs to closure
- Collaborate with all test teams to have complete coverage on integration areas
(V)alidation
- Execution of test cases is completed
- All appropriate bugs are tracked to closure
(E)xit
- All the BVTs passed on all the builds/patches
- Code Complete Build:
- Test should be able to execute 100% of test cases by end of code freeze build and 80% of test cases should pass
- By start of Test final build :
- All failed test cases of Code complete build + other test cases planned should pass.
- All bugs raised during the Code complete build execution should be resolved & closed
- No S1 & S2 bugs should be in proposed/active/resolved state
- Active S3 & S4 bugs count should be within permissible limit like 5% of total bugs or moved to future releases
- Any known issues with technical constraints or anything should have an agreed resolution
- Test Final Build:
- All planned test cases for final build should pass
- No S1 & S2 bugs should be in proposed/active/resolved state
- No S3 & S4 bugs should be in proposed/active/resolved state
Vijay Nagandla 