Determine location for Quality Management within site architecture
We are currently working through the MVC for Quality Management, and are investigating the best location for this new offering within our site architecture.
Quality management will be at the project level, and will eventually tie in with tests that are run within pipelines in order to show the status of various test cases for that project. As we expand Quality management, users will also be able to relate test cases to Requirements, which will help in identifying the impact of test failures on the project.
Current considerations for location
- Test cases will tie to tests being run within pipelines
- Quality management aligns closely with the CI / CD lifecycle, and is important in understanding when/how issues arose
- As we build out relationships between test cases and Requirements, it can make sense for these to live together
- However, some organizations may choose to not utilize Requirements or tie them to test cases. In that case, it wouldn't make sense for Quality to live underneath Requirements, and may reduce discoverability - especially since the Requirements section can be turned off.
Renaming current Requirements
section to Requirements & Quality
- Benefit of having Quality with Requirements as stated above
- Discoverability may be better than the previous options
- Still the question of what happens if a user turns off Requirements in project settings (do we rename the nav item to
Quality
at that point?)
- Provides room for expandability (view for test cases, for test sessions, reports, etc)
- Adds more clutter to our already expansive side navigation
Edited by Nick Brandt