Make it more obvious when a requirement is not covered by a test
It would be good if the table cell or text for the requirement status is colour coded to make it easy to identify requirements which are not covered, not ran etc.
anonymous
shared this idea
Hi,
Kindly note that this feature request was completed. From now on requirement statuses are capitalized and accompanied with relevant icons.
Best regards,
Christine
-
Anonymous
commented
Our three votes went to dealing specifically with this: requirements are currently associated with tests in the test library. We would find it to be more useful for requirements to be easily linked to test instances in test runs.
What we're really getting at is: for feature X in iteration Y, which tests are associated with feature X and what is the state of each test?
Currently, the system produces results that are incorrect in some cases and it's generally tedious to add groups of tests to requirements.
-
Kam
commented
+1 Was going to raise this myself