It's all about the answers!

Ask a question

Why does JRS report for a simple trace shows me non linked records?


anup Gaur (1392444) | asked Sep 21 '17, 1:30 a.m.

We are running CLM 6.0.1. i am creating a QM report in JRS using Test plan > Test Case > Test Execution Record > Test Case Result.


The result shows me TCERs for Test cases which do not have Test Plan(unassigned). Why is this happening? I thought that the trace ability relationship will make sure to select TCER which belong to that Test Plan only.


The TCER with ID 14275 has no Test Plan associated with it. This should be shown under Unassigned test plan and not under Test Plan A where the same "Test case 1" is used. Is this working as designed?

2 answers



permanent link
Francesco Chiossi (5.7k11119) | answered Sep 21 '17, 4:29 a.m.

Hello Anup,

the traceability link is enforced only between the 2 elements directly connected by the link.
If you want to enforce a condition between Test Plan and TCER you need to explicitly add it.

Best Regards
Francesco Chiossi


Comments
anup Gaur commented Sep 21 '17, 7:38 a.m. | edited Sep 21 '17, 8:05 a.m.

 Thanks for the info Francesco. 


I did get it finally by adding a common attribute like TCER.Test_plan_name and editing the SQL query.

Is there a GUI way to do this without editing the SQL_query. That will really help noobs in SQL  like me.


Francesco Chiossi commented Sep 21 '17, 10:29 a.m. | edited Sep 21 '17, 10:30 a.m.

One possibility you can look at from the UI is to build your traceability like this.
Unfortunately this is only available in 6.0.3 and later.


permanent link
Francesco Chiossi (5.7k11119) | answered Sep 21 '17, 10:17 a.m.

Hello Anup,

it looks like you cannot add the condition through the UI, so it has to be done on the SQL code itself.

SELECT DISTINCT T1.PROJECT_NAME,
       T1.REFERENCE_ID,
       T1.NAME AS URL1_title,
       T1.URL AS URL1,
       T2.REFERENCE_ID AS REFERENCE_ID1,
       T2.NAME AS URL2_title,
       T2.URL AS URL2,
       T3.REFERENCE_ID AS REFERENCE_ID2,
       T3.NAME AS URL3_title,
       T3.URL AS URL3,
       T4.REFERENCE_ID AS REFERENCE_ID3,
       T4.NAME AS URL4_title,
       T4.URL AS URL4
FROM RIDW.VW_TESTPLAN T1
INNER JOIN RIDW.VW_TESTPLAN_TESTCASE_LOOKUP LT1
ON (T1.TESTPLAN_ID = LT1.TESTPLAN_ID)
  INNER JOIN RIDW.VW_TESTCASE T2
  ON (T2.TESTCASE_ID = LT1.TESTCASE_ID)
    INNER JOIN RIDW.VW_EXECUTION_WORKITEM T3
    ON (T2.TESTCASE_ID = T3.TESTCASE_ID)
      INNER JOIN RIDW.VW_EXECRES_EXECWKITEM_LOOKUP LT2
      ON (T3.EXECWORKITEM_ID = LT2.EXECWORKITEM_ID)
        INNER JOIN RIDW.VW_EXECUTION_RESULT T4
        ON (T4.EXECUTION_RESULT_ID = LT2.EXECUTION_RESULT_ID)
WHERE (T1.ISSOFTDELETED = 0 AND T2.ISSOFTDELETED = 0 AND T3.ISSOFTDELETED = 0 AND T4.ISSOFTDELETED = 0) AND
(T1.TESTPLAN_ID <> -1 AND T1.TESTPLAN_ID IS NOT NULL) AND
(T2.TESTCASE_ID <> -1 AND T2.TESTCASE_ID IS NOT NULL) AND
(T3.EXECWORKITEM_ID <> -1 AND T3.EXECWORKITEM_ID IS NOT NULL) AND
(T4.EXECUTION_RESULT_ID <> -1 AND T4.EXECUTION_RESULT_ID IS NOT NULL)
AND (T1.TESTPLAN_ID = T3.TESTPLAN_ID)

The above is the query generated by a simple report using the traceability you described. The added condition to force the TCER to match the Tesplan is the last line.

Best Regards

Francesco Chiossi

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.