As an ASAP Developer, in order to provide FedRAMP reviewers easy confirmation that automated tools are addressed, I want to identify identify all automated tool findings.
Acceptance Criteria
[x] All Schematron assertion messages are declarative statements which affirm the positive test outcome.
[x] All Schematron assertion diagnostic messages are declarative statements which explain the negative test outcome.
[x] The Schematron code has no assertion failures when validated using src/validations/styleguides/sch.sch using the basic phase.
[x] XSpec unit tests for positive and negative Schematron assertion outcomes accompany all Schematron assertions (where feasible).
[x] observation with a method of 'TEST' has a type of 'finding' and an origin/actor/@type='tool'
[x] observation, method='TEST' and type='finding' has subject[@type='component'] whose @subject-uuid matches the uuid of a result/local-definitions/assessment-assets/uses-component
[x] observation, method='TEST' and type='finding' has subject[@type='component'] whose relevant-evidence/@href matches the uuid of the raw-tool-output resource in the back-matter.
[x] observation, method='TEST' and type='finding' has a @uuid value that matches a finding/related-observation/observation-uuid value.
Definition of Done
[x] Acceptance criteria met
[x] Unit test coverage of our code > 95%
[x] Automated code quality checks passed
[x] Security reviewed and reported
[x] Reviewed against plain language guidelines
[x] Code must be self-documenting
[x] No local tech debt
[x] Load/performance tests passed – needs to be created/automated
[x] Documentation updated
[x] Architectural Decision Record completed as necessary for significant design choices
Extended Description
Acceptance Criteria
src/validations/styleguides/sch.sch
using thebasic
phase.Definition of Done