Hello, in our current workflow an additional step between requirements and test cases is included. We call this "Test Definition" or "Test Strategy" in an early planning stage when the requirements are made, but the specific test cases have not been formulated. In these test strategies we describe what is supposed to be tested nd they can later lead to several test cases. Is there any way to include this additional layer in SpiraTeam. Also we would like this additional layer to be completely traceable between requirements and test cases. Best regards Sebastian Wandernoth 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/1497.aspxthreadId=1497Sebastian Wandernoth (sebastian.wandernoth@exco.de)associations coverage Hello, in our current workflow an additional step between requirements and test cases is included. We call this "Test Definition" or "Test Strategy" in an early planning stage when the requirements are made, but the specific test cases have not been formulated. In these test strategies we describe what is supposed to be tested nd they can later lead to several test cases. Is there any way to include this additional layer in SpiraTeam. Also we would like this additional layer to be completely traceable between requirements and test cases. Best regards Sebastian Wandernoth Thu, 14 Jul 2016 11:26:16 -04002016-07-18T07:51:55-04:00/Support/Forum/spiratest/issues-questions/1497.aspxmessageId=2687Jim R (donotreply5@kronodesk.net) Hi Sebastian You could make it a different type of "requirement" and simply use the Associations tab to link it to the requirement before the test cases are written. If there is always only a single strategy for each requirement, then a simpler option would be just add a long rich text custom property to requirements called "Test Strategy". Regards Jim Fri, 15 Jul 2016 18:19:36 -04002016-07-15T18:19:36-04:00/Support/Forum/spiratest/issues-questions/1497.aspx#reply2687messageId=2690Sebastian Wandernoth (sebastian.wandernoth@exco.de) Hi Jim, thanks for your answer. Unfortunately, the relations between requirements and strategies are n-to-m and the same is true for the relations from strategies to test cases. So we will definitely need an actual object in between. Is it somehow possible to create a custom artifact in SpiraTest? One of the problems with your solution (aside from it being a bit unintuitive having to create a new requirement when writing a test-strategy and we want to make the interface as simple as possible for the testers) is that the artifact ID would be that of a requirement. In our workflow we are tracing by requirement ID + strategy ID + test case ID. So it would be really beneficial if the strategy could have a distinct ID, too. But I guess now we are back to creating a custom artifact.... regards, Sebastian Mon, 18 Jul 2016 07:51:55 -04002016-07-18T07:51:55-04:00/Support/Forum/spiratest/issues-questions/1497.aspx#reply2690