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? Wed 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? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiratest/issues-questions/1793.aspxthreadId=1793Karl Tinsley (Karl.Tinsley@peci.com) 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? Wed 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? Wed, 10 Jan 2018 15:19:23 -05002018-01-12T18:11:34-05:00/Support/Forum/spiratest/issues-questions/1793.aspxmessageId=3206Jim R (donotreply5@kronodesk.net) Hi Karl, That is a good point. If you dont 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. Regards Jim Fri, 12 Jan 2018 18:11:34 -05002018-01-12T18:11:34-05:00/Support/Forum/spiratest/issues-questions/1793.aspx#reply3206