Leaving this for GSA. Items in Automation Guide are not in final format and not expected to be before close out of project.
Extended Description
Many of the issues created in the FedRAMP Automation Guide (private) have responses. These need to be examined against existing validations for edits and enhancements.
Preconditions
This might require new issues for each section of the Guide with feedback. Otherwise it will get unwieldy.
Acceptance Criteria
[ ] All Schematron assertion messages are declarative statements which affirm the positive test outcome.
[ ] All Schematron assertion diagnostic messages are declarative statements which explain the negative test outcome.
[ ] The Schematron code has no assertion failures when validated using src/validations/styleguides/sch.sch using the basic phase.
[ ] XSpec unit tests for positive and negative Schematron assertion outcomes accompany all Schematron assertions (where feasible).
More acceptance criteria…
Story Tasks
[ ] Tasks…
Definition of Done
[ ] Acceptance criteria met
[ ] Unit test coverage of our code > 95%
[ ] Automated code quality checks passed
[ ] Security reviewed and reported
[ ] Reviewed against plain language guidelines
[ ] Code must be self-documenting
[ ] No local tech debt
[ ] Load/performance tests passed – needs to be created/automated
[ ] Documentation updated
[ ] Architectural Decision Record completed as necessary for significant design choices
Leaving this for GSA. Items in Automation Guide are not in final format and not expected to be before close out of project.
Extended Description
Preconditions This might require new issues for each section of the Guide with feedback. Otherwise it will get unwieldy.
Acceptance Criteria
src/validations/styleguides/sch.sch
using thebasic
phase.Story Tasks
Definition of Done