Relationship between Requirements and TestCases

[daas]

Hi, May be I overlooked something but I can't find how to link one or more requirements to a testcase. The relationship matrix offers no possibility to create direct relationships between Testcases and Requirements. May be someone can help me?

[RoyC]

Can you be more specific about what you are doing?  

I can drag Requirements and Test Cases from the Custom Elements page of the Toolbox, and I can create Association and Realization relationships between them. I can also go to the Relationship Matrix and delete those relationships, and recreate them.

In the Relationship Matrix I have the source and target packages defined, the source and target elements set to Test Case and Requirement, the Link Type set to Association or Realization, and the Direction set to Source -> Target or Target -> Source.

Note that you can't create a relationship on the Matrix if the direction is set to Both.

At what point does the problem arise?

[daas]

Thanks, your answer was very helpfull

[daas]

Roy,

When I open the relationship view I can browse to the requirements package(s), but it is not possible to browse to testcases and indicate the source or target packages (or something else where the testcases can be found).

[RoyC]

Can you make full use of the Relationship Matrix for other element relationships, like Use Case realizes Requirements?  There is nothing about Test Case elements that would stop you fully using the RM options. I can't see why the Matrix would work for some element types but not others.

If the Matrix won't let you select Source and Target packages, there is something wrong and you should submit a bug report or support request.

[daas]

Roy,

I don't have problems with testcases from the custom toolbox, but with tests as specified in the test view. But I will change our way of working and specify our tests via testcases from the custom toolbox. That will satisfy our needs.

So thank you for your help,

Best Regards, Daan

[RoyC]

'Oei Daan

Aha! Now I see.

A Test Case element has a number of advantages: you can define a test once that applies to several elements, so you don't have to keep typing the details either of the test or the scenario from which you can generate the test. You can link the test to document files, linked documents and document artifacts elements that are exclusively concerned with either that test or the test plan. And the Test Case element and its relationships can be specified in the Relationship Matrix and the Relationship Hierarchy Window.

An internal test script is a tightly bound feature of its parent element and applies to nothing else. You don't have to look for relationships or other elements anywhere else to see where it is. If you have policies and procedures that define how and where to record test scripts, you know exactly where to find them.

As you say, you can adopt a policy of defining test scripts within Test Case elements so that you add the advantages of the element to the specificity of the internal script. You would not necessarily have to locate the Test Case elements in the Relationship Matrix, but that would be a good way to make sure every element subject to testing had a defined test script.

'dag

[daas]

Roy,

I agree with your comments. But thanks to you I found the Test Case in the Custom toolbox. So it is not so obvious that this exists. I was focused on the tests in the testview trying to specify tests and relate them to requirements, use cases, business rules, etc.
I think a reference in the help documentation would have been of much help for me in this case.

Best regards and thanks
Daan