Metadata on SSD Landing Criteria
Feature Branch Exit Criteria
The following criteria must be met before considering landing the feature branch into master.
Exit Criteria | Status/Notes |
|---|---|
Test automation and CI is 100% complete with “required for version” | Done for 2.4 |
No defects with high/critical exposure or “required for version” | |
No new daily or weekly regression test failures in PMDK mode | daily (3 new + 9 existing ones) |
All tests are passing or failure are triaged/waived/documented with MD-on-SSD feature in weekly and daily regression tests | daily (3 new + 9 existing ones) |
Performance and scale testing executed according to test plan/required requirements. Results are reviewed and approved. (Lenox) | TBD |
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. | Tickets from first pass all addressed. Will need to re-run on final code before merge. |
SAFE review executed if required | SAFE review is not needed. |
Any new dependencies identified and Oked by ESAD OSPDT owner | New dependence on lmdb, looks like OpenLDAP licence No other new dependencies except PMDK allocator copied to the code. |
Does not regress endurance testing from current master baseline with feature enabled | Soak test in progress. Issues under investigation. |
Does not regress scale testing from current master baseline (Frontera) | Create a ticket with relevant information (commit/branch to test and any special considerations) and assign to Dalton. |
Manual test plans and “out-of-box experience” testing are 100% executed with “required for version”. Manual test results are recorded | All tests should be automated
|
Feature branch is up to date with master | Merge with master |
Feature Completion Criteria
The following criteria must be met before considering the feature is complete
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. | DONE |
Planned software feature is 100% implemented with “required for version” | DONE |
All user documentation updated and reviewed (e.g., admin guide, user guide) | Still gaps in the documentation. |
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 | DONE |