Test Case to associated requirements in RQM 5.0
With the upgrade to RQM 5.0; the testcase/requirement/href has been removed in RPE. This was used in the template to go from test case to the requirements associated to the test case. I can iterate over my requirements to discover the test cases that validate it; however, I can no longer iterate over my test cases to discover the requirements associated to it. We have over 20 test cases in our test plan and 900+ requirements. I do not want to iterate over all my requirements to find a match each time I iterate my test case.
With the testcase/requirement/href removed, how do you traverse from Test Case to the associated requirements? The outline to my test document looks like this: Test Plan Test Plan Details Test Suite(s) ( In execution order) Test Suite Details Test Cases (In execution order) Test Cases Details (w/ associated requirements) Test Scripts Test Steps Test Cases (Stand Alone-not associated with Test Suites in previous section) Printed in execution order Test Case Details ( with associated requirements) Test Scripts Test Steps The template is almost complete- just need the table of associated requirements for the testcase. |
2 answers
Hi Erica,
I presume you are seeing this issue after doing "Replace Schema..." from Outline view in RPE Studio. testcase/requirement/href is still available if you are adding a new RQM 5.0 schema. But if you are using RPE 1.2.1.1 or earlier versions and do a upgrade (replace) of schema, the schema will be incomplete. This has been fixed in RPE 1.3. You can choose any of these options: 1. Upgrade RPE to 1.3 IFix 01. 2. Use any workaround to replace schema in RPE. 3. Open the schema in editor and modify as of RQM 5.0. |
|
Workaround #1:
1. Create a new template 2. Add a new schema, naming it exactly as in the old template 3. Open the old template, select the template element and copy paste them into the new template 4. Tell RPE to use the new schema instead of the old schema. Workaround #2: 1. Rename the current QM schema to _old 2. Add a new QM schema by pulling the latest version from RQM server 3. Re-establish data source configurations and high level containers for the schema being replaced. 4. Copy and paste lower level containers from the _old schema to the new schema. Workaround #3 (This will always work): 1. in Studio select the data source in the Outline view and right down the URI property 2. unzip the dta file 3. in the schema folder identify the folder obtained at step 1 4. edit the schema using notepad or whatever XSD editor you prefer to add what is missing 5. zip the template again and rename to dta |
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.