Skip Navigation LinksHome Page > Forums > SpiraTest Forums > SpiraTest Issues & Questi... > How to handle items that ...
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?
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.