Adding end to end tests for common trestle use cases can catch early bugs and regressions increasing release quality. Suggesting this be added as a validation step to release pull requests.
Caveats / Assumptions
This could be added to all pull requests, but may slow execution. Unit testing here might be enough.
Completion Criteria
Identify critical workflow test cases to include
Any generated OSCAL documents should be validated against the relevant JSON schema for the currently supported version of OSCAL
Issue description / feature objectives
Adding end to end tests for common
trestle
use cases can catch early bugs and regressions increasing release quality. Suggesting this be added as a validation step to release pull requests.Caveats / Assumptions
Completion Criteria
oscal-cli
Triggered by #1606