Product Idea

Expand all | Collapse all

Test Case step related to Requirement

  • 1.  Test Case step related to Requirement

    Posted 01-20-2016 05:50
    Hi everyone.

    Is there any way to relate a test case step to a requirement? For example, I want to create the TC1 that step 3 may verify the REQ1 and step 10 the REQ2. Is it possible? Is there any other way to create this relationship?


  • 2.  Re: Test Case step related to Requirement

    Posted 01-20-2016 06:31
    No, there isn't.
    If you need to ensure traceability you would need to separate the steps into separate test cases.

  • 3.  Re: Test Case step related to Requirement

    Posted 01-20-2016 12:29
    Anna's suggestion makes sense to me.  The question we try to ask is "what set of things do we want to be able to report as distinct failures?"  We have some test cases we are trying to split up as time allows to reflect this.

    We informally (and not consistently sadly) use the notes field when we have many requirements linked to a test case, to note which requirement drives each step.  If a step fails, we've found it a little tedious to look through a long list of related requirements to figure out which are tied to the failure.


  • 4.  Re: Test Case step related to Requirement

    Posted 01-22-2016 05:46
    Thanks Anna and Bob for the information!!

  • 5.  Re: Test Case step related to Requirement

    Posted 06-22-2016 19:01
    I would also find it useful to be able to cite a defect report number/link at that same step which points to a requirement.

    In this way a reviewer could follow along a test run and see when steps failed which requirement was connected, and that a defect report was filed against that failure, and which defect report.

  • 6.  Re: Test Case step related to Requirement

    Posted 06-23-2016 11:53
    Thanks for providing some context around this, szawasky. It sounds like people would love to see Test Steps act more like discrete items than item fields...

  • 7.  RE: Re: Test Case step related to Requirement

    Posted 07-12-2017 12:11
    Edited by Steve 07-12-2017 12:12

    We currently address this as Bob describes, using the Notes field.  Yes, we're forced to settle, which is unfortunate considering all the untapped Jama potential in this area.  

     Imagine this:

    1.  I trace / create a relationship from each requirement (or design decision, or whatever is to be verified by test) to the particular test step or steps that verify it's satisfaction, so now:

    a.  If a [linked to / related] test step changes, or the item traced to it changes, the "to" and "from" items, as well as the link/relationships themselves are flagged as suspect (with a pop-up, email, something conspicuous - it's user/admin configurable) which tells me that an important requirement may no longer be adequately tested. Since I have 10, 20, 30, 40, or more requirements tested by this test case, if a single test step or requirement changes, I need only investigate the items linked / related to that changed item rather than all test steps or all requirements, as must be done now when linking the entire test case.  True, test cases could be broken down into smaller units but that's not always practical, and essentially puts a much greater burden on the user who'd rather use a tool to alleviate such burdens.

    b.  Verifying proper traceability becomes less burdensome and traceability (and coverage view) reliability increases significantly. I no longer must spend extra time trying to 'figure out' where / how / if each requirement that traces to a test case, including the one just created to fill a hole seen in Coverage View, is actually addressed somewhere within the test case.

    2.  I look at a requirement /item's test tab and see if / when that particular item was tested, whether it passed (satisfied) or failed, under what conditions (i.e. the test date/time, the test case and version, etc.) I can now more easily compare the test history for this particular item, as well as its version history, with other 'system' changes or conditions – this helps in troubleshooting and root cause analysis, among other benefits.  I can of course do this without the new 'trace-to-step' feature, but not as seamlessly.

    3.  I generate reports and charts showing test status of individual items, and patterns, and more – essentially the same type of reports and charts that I could generate external to the tool, but now at a fraction of the time and effort. I can more readily respond to customer status requests, or better yet, they can see more directly for themselves.

    4.  I'm happier, and less frustrated! My customer is happier, and impressed!

    P.S.  @Kristina


  • 8.  RE: Re: Test Case step related to Requirement

    Posted 07-12-2017 16:03
    @Steve thank you for this novel of feedback you promised! Good points.

    Kristina King
    Jama Software

  • 9.  RE: Re: Test Case step related to Requirement

    Posted 07-13-2017 07:35
    @Kristina Hopefully it leads to a non-fiction masterpiece!