How to handle items that cannot be tested.

Wednesday, January 10, 2018

We occasionally have requirements that cannot be tested for various reasons. We still want to keep track of them and report them as part of our risk assessment. What is the best way to handle these in SpiraTest? We'd like to be able to have the requirement in the list, with a status or flag of some kind that it is untestable. Another option would be to create a test case for the requirement, and flag the test case as untestable. Any suggestions?

1 Replies
Friday, January 12, 2018
re: karltinsly Wednesday, January 10, 2018

Hi Karl,

That is a good point. If you don't have a test case then they will show up in the Not Covered metrics. You could put it in state "Obsolete" but that is not ideal. So I would probably write a test case and link to to them, and make the test case an inactive status such as "Rejected". Or run the test case and assign the status N/A.



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: Wednesday, January 10, 2018
  • Last Reply: Friday, January 12, 2018
  • Replies: 1
  • Views: 1434