Catastrophic Recovery Landing Criteria

Owned by Fan Yong
Last updated: Apr 11, 2024
2 min read

Feature Branch Exit Criteria

The following criteria must be met before considering landing the feature branch into master.

Exit Criteria

Status/Notes

Exit Criteria

Status/Notes

Test automation and CI is 100% complete with “required for version”

Done. (PR#13718 & PR#14080)

No defects with high/critical exposure or “required for version”

Done. (PR#13718 & PR#14080)

No new daily or weekly regression test failures (failures not already on master branch)

Done. (PR#13718 & PR#14080)

All tests are passing for feature in weekly and daily regression tests

Done. (PR#13718 & PR#14080)

Performance and scale testing executed according to test plan/required requirements. Results are reviewed and approved

Done. (Dalton)

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.

Run coverity on feature branch (AR: )
Run Snyk on feature branch (AR: )

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

Perform SOAK test. (Maureen)

Does not regress scale testing from current master baseline with feature enabled

Perform large scale test on Aurora (Makito)

Manual test plans and “out-of-box experience” testing are 100% executed with “required for version”. Manual test results are recorded

N/A, all new test cases are automated.

Feature branch is up to date with master

Merge with master. (Nasf & Kris)

Feature Completion Criteria

The following criteria must be met before considering the feature is complete.

Exit Criteria

Status/Notes

Exit Criteria

Status/Notes

Requirements are defined in SRS Jira Project.

Done.

Design document is complete, reviewed, and approved utilizing the team template.

Done.

Test plan for feature is complete, reviewed, and approved utilizing the team template. Security validate plan is also updated if applicable.

Test plan had been discussed with the team. All tests had been automated. (Makito)

Planned software feature is 100% implemented with “required for version”.

Done.

All user documentation updated and reviewed (e.g., admin guide, user guide).

 

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.

 

Usability is evaluated and results are reviewed.