Defining the acceptance criteria for any project for release becomes a very difficult ask. The acceptance criteria is so because , not all project can have the same acceptance criteria, yet the client expects the same acceptance criteria for all projects. This is the irony.
In any case, the following list can be used as a starting point, with some variations
Acceptance Criteria | Goal/Target | Status |
Code/ Feature completion | 90 % of the planned code/feature to be completed | Accomplished more than 90 % planned code and have a mutual understanding for the remainder. |
BVT cases pass | 100 % BVT cases pass | 100 % BVT cases passed. Refer the attached results |
Final Test Pass | 85 % Test cases pass | 95 % passed in the final release build. |
Bugs Resolved and closed | 90 % of P1-S1 & at least 70 % of P2-S2 bugs should be resolved and closed | Criteria met, 732 defects regressed & verified. |
Bug convergence | a. The number of open defects to be decreased in the last two weeks. | Criteria met. The bug convergence graph is depicted |
Code Coverage | 70 % block coverage from Automation & Manual testing | Criteria met. The combined code coverage is 74% . |
Automated Test cases % | 60 % of the test cases are automated which are identified for automation | Criteria met. 65% cases were automated |
Automation pass % | 80 % of Pass of Automation Test Suite | Criteria met. 81 % pass achieved. |
Reliability Index for automated cases | 90 % for previous sprint and 75 % for current sprint to be achieved | Criteria Met. 97 % for previous sprint and 78 % for current sprint. Refer Health index |
All Test code checked in | Refer branch | |
Any explicit Performance /Security parameters called out in SOW |