Skip Navigation LinksHome Page > Forums > SpiraTest Forums > SpiraTest Issues & Questi... > Additional layer between ...

Additional layer between Requirement and Test Case

Thursday, July 14, 2016

associations

coverage

Sebastian.Wandernoth

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

2 Replies

Friday, July 15, 2016

~~inflectra.jimx~~

re: Sebastian.Wandernoth Thursday, July 14, 2016

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

Monday, July 18, 2016

Sebastian.Wandernoth

re: inflectra.jimx Friday, July 15, 2016

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

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

Statistics

Started: Thursday, July 14, 2016
Last Reply: Monday, July 18, 2016
Replies: 2
Views: 1739

Additional layer between Requirement and Test Case

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

Edit Thread

Edit Message

Search Results