Adding Tests based on the Requirements to a release/iteration

Monday, June 17, 2013
Hello dear reader ;)

I did add some requirements to the requirement list and added test for each requirement.
With this I can see the coverage and test progress for each requirement which is good.
Now I add requirements to a release or iteration and would expect the test information gets linked as well.
But when I create a test set from that release or iteration it is just empty. Also in the release or iteration list I get shown no coverage for tests.
Is it me doing something wrong or is it the tool not supporting this way of using the requirement-test linking information.
It feels like redundant and risky to me to have to add the tests again and can not rely on the requirement-test linking in the first place.

Thanks for any type of feed back.
1 Replies
Thursday, June 20, 2013
re: werner.oswald Monday, June 17, 2013

Hi Werner

You are correct, you need to also add the items to the Release/Iteration.

Usually this is because the requirement is only linked to one Release (the one the functionality was introduced in), whereas the test cases are generally linked to all releases that the functionality needs to be tested in - including regression cases.



Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Monday, June 17, 2013
  • Last Reply: Thursday, June 20, 2013
  • Replies: 1
  • Views: 2882