The Covered requirement field in a test suite can be contradictory to test cases
Requirement Documents: "Visa", "MasterCard", "American Express"
Manual Test "Visa Card Checkout" -> Covered requirement -> "Visa"
Test Suite "VIsa Card Checkout Test Suite" -> Covered requirement -> "MasterCard"
You can assign a different covered requirement to a Test Suite than you can to a Manual Test. How can you cover a requirement in the test suite that wasn't covered in a test?
It seems the Covered requirement on the test suite should either:
1) be removed
2) be a reference from the test case and not a field you can populate
I think this should be made possible with business rules.
For example, you should be able to add a business rule that collects the req. coverage from all tests and updates the req. coverage of the suite.
We have this on the roadmap. Changing to "Waiting for Votes" to see how common the need is.
Meanwhile possible workarounds could be
- make this field read only
- add a webhook that performs the update based on aggregated coverage, as mentioned above