...
Requirements are defined in SRS Jira Project
Design document is complete, reviewed, and approved utilizing the team template
Test plan for feature is complete, reviewed, and approved utilizing the team template. Security validate plan is also updated if applicable.
Planned software feature is 100% implemented with “required for version”
Test automation and CI is 100% complete with “required for version”
No defects with high/critical exposure or “required for version”
No new daily or weekly regression test failures (failures not already on master branch)
All tests are passing for feature in weekly and daily regression tests
All user documentation updated and reviewed (e.g., admin guide, user guide)
Performance and scale testing executed according to test plan/required requirements. Results are reviewed and approved
SDL Code scans are competed (Coverity, Bandit, Checkmarx, Snyk). For all scans, all issues have been dispositioned, and the issues that are required per SDL rules have been fixed.
SAFE review executed if required
Any new dependencies identified and Oked by ESAD OSPDT owner
Does not regress endurance testing from current master baseline with feature enabled
Does not regress scale testing from current master baseline with feature enabled
Code coverage results have been reviewed to identify gaps in testing, and test plan has been updated and executed accordingly. Functional and branch coverage each are equivalent or better than master
Manual test plans and “out-of-box experience” testing are 100% executed with “required for version”. Manual test results are recorded
Usability is evaluated and results are reviewed