Test Management 2.0: associate defects to test cases

[Mike304]

In Test Management 2.0, how can you relate Defects (rm_defect) to Test Cases (sn_test_management_test)? The documentation is very clear on how to execute your tests in sprint testing and categorize the test runs as passed/failed/blocked, but if a test fails how do you track the issue to resolution and retest if you can’t tie it to a defect?
NOTE: We are not using Test Management 1.0

[Frank67 · Accepted solution]

Can't be done Mike. This is a common gripe with Test Management 2.0 and hopefully one day soon it will start to pick up some of the functionality that Test 1 offers and which testers expect as standard.

The closest you can get is hooking it to a test execution suite which holds the tests, but if you are adding tests to stories in the agile board you won't even be using those.

We use test execution suites with a  defects related list and also link defects to stories. Our advice to testers is to raise the defect in a second screen and copy and paste the defect number and description into the comment on the failed test step, and ensure the test name is included in the Defect description to help the devs know what they are resolving.

[EdoM]

Hi Mike, You can raise a new requirement in the idea portal, I'd support it!

[Mike304]

Idea "Test Mgmt 2.0: relate Defects (rm_defect) to Test Cases (sn_test_management_test)" submitted!

[Allison2]

Mike,

You can have defects tied to stories.  Then when you find a defect report it directly under the story itself so you have some traceability.  That's how we'll be doing it until we have the capability to report it directly from the test.