...
Exit Criteria | Status/Notes | |
---|---|---|
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 |
| |
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 | SAFE review is not needed. | |
Any new dependencies identified and Oked by ESAD OSPDT owner | No new dependencies | |
Does not regress endurance testing from current master baseline with feature enabled |
| |
Does not regress scale testing from current master baseline with feature enabled |
| |
Manual test plans and “out-of-box experience” testing are 100% executed with “required for version”. Manual test results are recordedAll tests should be automated | ||
Feature branch is up to date with master |
|
...