Skip to main content
S
ssaul15-Moonstone
15-Moonstone
October 20, 2015
Solved

ALM: trace between input and test case not possible

  • October 20, 2015
  • 1 reply
  • 1534 views

We are using the ALM solution and found that creating traces between inputs (input documents) and test cases are not possible.

Traces can only be added between requirements or specifications and test cases.

Traces from inputs can only go to requirements or specifications, not to test cases.

Does anybody know a possible reason?

 

We could add traces (Validated By / Validates) to inputs via administration, but what else has to be done to get traces between inputs and test cases to work?

 

Any help is appreciated.

 

Stephan

Best answer by VolkerEckardt

Hi Stephan,


there is a reason for this setup: Input = Wish list from client. Requirement = commited work. Tracing between wish list items to test cases is nice, but not needed from a functioal / process point of view, and will lead to incorrect assumptions.


From Input you define Requirement (trace) and then from Requirement you derive Test cases (trace).


I think the setup you did is technically speaken all right and shall be suffcient. Validate  if the suspect flag appears when you change an input entry. But again : Input = Wish list from client.


Volker

1 reply

V
VolkerEckardt17-PeridotAnswer
17-Peridot
October 21, 2015

Hi Stephan,


there is a reason for this setup: Input = Wish list from client. Requirement = commited work. Tracing between wish list items to test cases is nice, but not needed from a functioal / process point of view, and will lead to incorrect assumptions.


From Input you define Requirement (trace) and then from Requirement you derive Test cases (trace).


I think the setup you did is technically speaken all right and shall be suffcient. Validate  if the suspect flag appears when you change an input entry. But again : Input = Wish list from client.


Volker

    Terms & ConditionsAccessibility statement