Spike - Linking Requirements and Test Cases
Problem to Solve
As users adopt requirements, they have been asking how to best show both implementation and verification of these requirements. At present, it's possible to run a report in the CI/CD Pipeline to mark a requirement as passing or failing based on the output of the test within the pipeline. While this is a very powerful feature, this does not allow for test planning, test scheduling or showing where a requirement was implemented.
Desired Outcomes
As this problem has proven to be somewhat large, we would like to complete a spike effort to explore options, and put together a plan for satisfying the following criteria:
- Allow users to link test cases to requirements. This will enable test planning to occur.
- Allow users to link issues and/or merge requests to requirements. This will enable us to display a list of where the implementation was done / modified on requirements themselves.
Having this ability would allow for reports such as:
- A requirement is being updated. What test cases need to be updated as well? (regression analysis)
- A test case has failed in production. What requirements are no longer being met (noncompliance), and what changes to the implementation have recently been made?
This issue description will be continually updated throughout the spike process as we learn what possibilities exist and further refine our plan.
Deliverables
Next Steps
The plan for moving forward will be documented in the parent epic for this issue.
Related information
- Initial Direction Meeting (GitLab unfiltered login required)