In the last week it so happened that I spent a lot of time working with RQM. I’ve created a number of templates in the process and I want to share the most interesting three here.
The templates were created and tested using CLM 5.0.2 and are available on the RPE Developer Works Wiki here.
How to print basic test plan information
Prints basic information about the test plan and its test cases. The test cases are retrieved using the efficient QM native filtering which allows RPE to gets all the test cases associated with the test plan in a single request.
Note that the test plan data source has metadata information that allows the end user to select the test plan from a list rather than typing it.
How do dynamically get state labels for test plans, test cases etc
Prints the test plans and for each their state. The state labels are read from RQM instead of being inferred from the state identifier.
How to print the requirements from a requirement collection associated with a test plan
Prints basic information about a test plan and its linked requirements. The requirements are read from from the requirements collection associated with the testplan.
When starting with DNG and document generation or when deploying new reports on the server the RRDG log is an invaluable resource for troubleshooting problems on the RRDG server. As expected the log provides detailed information on errors and additional information including performance data.
All the DNG logs can be access at https://server:9443/rm/logs. The log for document generation is rrdg.log which is located towards the end of the list.
By default the RRDG log is set on WARN level which means only warnings and errors will be logged. This is the recommended setting for most production servers but if you need to troubleshoot document generation you should increase the level and set it to INFO.
So what is the problem? The answer is in the Rational Quality Manager Reportable REST API Documentation. For efficiency reasons RQM does not return the link information by default. If you want to create traceability documents you’ll have to explicitly ask for the link information using the calmlinks argument in the request URL.