THIS IS WORK IN PROGRESS DOCUMENT
Feature Branch/PR Exit Criteria
The following criteria must be met before considering landing the feature branch/PR into the master.
Exit Criteria | Status/Notes |
---|---|
Test automation and CI is 100% complete with “required for version” | Some tests exist, mostly system tests, but tracking % complete pending having a test plan |
No defects with high/critical exposure or “required for version” | None, but may be more filed as testing done |
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 added. |
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 recorded | Manual testing done by developer, but pending test plan for additional testing |
Feature branch is up to date with master |
|
...