RPE: In a Test Case document, how do you show linked requirements?
In RQM 5.0, using the QM datasource, testcase/requirement is depreciated (it does not return anything).
We have test cases linked to one or more requirement artifacts in DNG. I just need the artifact id and the artifact title for the test document.
So my question is, how can I get the requirement information for a test case? I am thinking I may need to use a DOORS datasource, then somehow query on links "validated By", but I have found no examples on how to do that.
Accepted answer
From QM data source, you CAN still get the requirements url. Please use testcase/requirement/href that will give https://server:port/rm/resources/ID. Use Script Expression to replace "/resources/" with "/publish/text?resourceURI=" and set it as the URI for Data Source Configuration element (RM data source). Also note that you should set data source type to REST (instead of generic XML) so that RPE calculates the URL to include all attributes used in the template.
Another way is to traverse from DNG to RQM. In this case, you may use datasource/artifact/traceability/links/ValidatedBy from the RM resources data source to get corresponding test case details from QM. You may find https://jazz.net/library/article/1241 useful.
I can share a screenshot / sample template if you face any issues.
Cheers,
Prasad
Comments
Thank you for your response. I am trying the first option, since it would probably be the most efficient. Unfortunately, I cannot get it to work. I am using RPE 1.2.1 with RQM 5.0 and DNG 5.0.
My QM Datasources are Generic XML:
https://server:port/qm/service/com.ibm.rqm.integration.service.IIntegrationService/schema/feed.xsd
https://server:port/qm/service/com.ibm.rqm.integration.service.IIntegrationService/schema/qm.xsd
Note: in RPE, testcase/requirement is marked as Depreciated, and to be removed as of RQM 4.0. However, as you state, testcase/requirement/href appears to still contain valid data.
I created a REST datasource for DNG. Using:
https://server:port/rm/publish/text?metadata=schema
url set to
href.replace( "/resources/", "/publish/text?resourcesURI=" )
The generator times out:
https://server:port/rm/publish/text?resourcesURI=_Z0OBEOxVEeS4DdzxJpfFKg&fields=dataSource/artifact/(title%7C@itemId)
Same in a browser. Is the datasource correct for DNG?
Answering myself. I had a typo. The correct script is:
href.replace( "/resources/", "/publish/text?resourceURI=" )
the datasource appears to be much slower though. The document takes quite some time to be generated when using this REST Datasource.
Thanks for you hlep
1 vote