how to manage the same test case associated to 2 different issues

[Shirin Younatani]

Hi, 

I wonder if we have a way to distinguish between the result of tests that cover 2 different use cases. 

to illustrate my question:

Issue #1 - AAA

Issue #2 - BBB

Test Case #3- Can Cover both Issue#1 and Issue #2, but Issue#1 test result is passed and for the second issue it's failed. So the status of this test case (#3) it's also passed and also failed. So what is the best case to manage this situation? we want to avoid adding duplicated tests only because of this limitation.

Thanks 

[Shirin Younatani · Accepted solution]

We found a better way, we just create a test plan for each release and their ticket and at the Test Coverage scope we choose to display the status according to the test plan and not a final one, and if at the same test plan we have 2 bugs with the same steps, maybe we need to consider the steps, to distinguish between them 

[Stefan Salzl]

Hi @Shirin Younatani ,

some questions:
how could one test case cover 2 use cases? Isn‘t a test case reflecting a use case? What is the difference between the use cases? 

I would question the plausibility if the test case REALLY covers both use cases (especially the result). Regarding your description obviously it doesn‘t.

Best
Stefan

[Shirin Younatani]

Hi Stefan, 
Thanks for your reply! 
We found a better way, we just create a test plan for each release and their ticket and at the Test Coverage scope we choose to display the status according to the test plan and not a final one, and if at the same test plan we have 2 bugs with the same steps, maybe we need to consider the steps, to distinguish between them 

thanks 

[Stefan Salzl]

Hi @Shirin Younatani 

Good to know you found a solution.

In order to mark this question as completed could you either accept the answer or write your solution into a new answer and accept your provided answer/solution?

Thanks in advance.

Best
Stefan

[Shirin Younatani]

Sure, thanks Stefan