How to handle tests for changed requirements, or requirement change process overall

Friday, December 18, 2015
Hi, I'm evaluating SpiraTest / SpiraTeam but there is one thing I can't figure out.

How to handle test cases for a requirement? 

Example: I have created a test case linked to a requirement, the test case is executed then the requirement changes. There seems to be no way to trigger an event for this change? How do I know which tests to re-test? Can I find the associated tests for a changed requirement by filter/search somehow? If not, is there any other recommended way to handle requirement change? I can't seem to find a way to handle requirement versions, e.g. v1 of the test case is executed towards v2 of the requirement? What is best practice in SpiraTest for this?

1 Replies
Wednesday, December 23, 2015
re: mmr Friday, December 18, 2015
Hi Mikael

There is no event currently triggered (planned enhancement) however you can run a Requirements Traceability Report and then see which of the test cases needed to be executed based on requirements that changed in a specific date range?



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: Friday, December 18, 2015
  • Last Reply: Wednesday, December 23, 2015
  • Replies: 1
  • Views: 1753