Is There A Way To Show Related Defects On A New TCER?
Hello,
Reading through the documentation listed here: https://www.ibm.com/support/knowledgecenter/en/SSYMRC_6.0.3/com.ibm.rational.test.qm.doc/topics/qm_c_defects_reports.html
it mentions that related defects are associated to a particular TCER. Is there a way that when the tester creates a new TCER, they can see the related defects that have been found on that particular test case in the right hand window? My testing shows that the only time the "Related Defects" will populate is if you are using the same TCER, and I'm hoping it can go across TCER in some way.
I tested this on our current version of 5.0.2, but it appears that this is also a problem with 6.0.3.
8 answers
Hi Dawn,
I am not sure what do you mean by "This answer may impact testing of your team" !!
However, the screenshot above shown is of a TCER which is not yet Run, but shows a related defects list which are open and are associated with the TCERs which are already executed for this particular test case.
RE Point 1) The example shown is of a new TCER and as of now no defects are linked to it yet, but the related defects listed are part of the another TCER which is part of the same test case.
RE Point 2) This link might help more in clearing the doubts : https://www.ibm.com/support/knowledgecenter/en/SSYMRC_6.0.4/com.ibm.rational.test.qm.doc/topics/c_check_dup_defect.html
Thanks,
Krupa Gunhalkar
Hi James,
Related Defects is displayed as mentioned by you on the right had side in a frame like UI for the NEW TCER as well if that particular test case has failed before and has an associated defect in its previous TCERs as shown below. So yes, as you mentioned, any TCER associated with that particular test case will display the Related Defects data as shown below.
Thanks,
Krupa Gunhalkar
Krupa,
Hi Krupa,
Hi Nguyen,
Yes Not Run TCER is different from "ran TCER" as it would have been serving different purpose for different iterations. Meaning, Not Run TCER might have been created by a test lead for upcoming sprint where in the already "ran TCER " might be for the current sprint or previous sprint. There are cases where you can create TCERS for the same test case for each sprint though you know the defect is not yet fixed. But to have the coverage and for tracking purpose, we need to create TCER and run it as well and may be sometimes the issue might crop up totally different altogether in the next iteration.
I am attaching one of the screenshots where you can Browse teh TCERs table list view with the showed columns where it shows different TCERS for the same test case with the Final Verdict being Diff. And also you can see a defect column which will list the associated defects for that test case for a particular TCER.
Also, if you open the test case, and check the TCER section of the test case, Related Change Requests panel shows all the defects logged for this particular test case.
Hope this helps.
Hi James,
As shown in the Very first answer to this question, Related Defects panel should show information of the defects and I have attached screenshot as well while running a TCER.
If for any case it is not displayed the required information on your setup, please raise a defect for it.
Thanks,
Krupa Gunhalkar
Thanks Krupa, it is useful