print custom section in RQM using RPE
![]() I asked a question in developerWorks RPE forum but wanted to ask on RQM forum as well: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=456942&tstart=0 |
7 answers
![]()
Rich text custom sections can be extracted by RPE as long as they are present in the schema. A custom section will be present in the schema only if it was added through a testcase/testplan template. Custom sections added to individual testcases/testplans cannot be reported on.
|
![]() This is the screenshot I have got from RPE version 1.2. I would like to create an attribute under testplan as richtext object used for customized section. I can create one under content directory (parent directory of testplan) but not under tesplan directory. Could you please provide further instruction about how to create? Thanks a lot. |
![]()
I am updating the answer from Chong Yuan as below. Many thanks to ChongYuan for providing the answers which helps the issue. Hopefully it will also benefits to other users who are interested in the same topic.
==Answer==== The testplan referenced in the feed schema actually locates in another schema file, so you need to edit the referenced schema file. But I don't find from RPE where to open that file directly. Here is something you can do to edit the schema outside of RPE, it's kind of of complicated though.. 1) inside RPE right click on the schema file in outline view, select 'open schema in editor', the schema file name will appear: ![]() 2) locate your .dta file, it is actually a zipped file so you can open it using tools like 7-zip, and find the schema file matching the name in step 1) under \schemas fold 3) open the _RPE_MAPPINGS_ file, and find the schema file matching 'https://clm.jkebanking.net/qm/service/com.ibm.rqm.integration.service.IIntegrationService/schema/qm.xsd'. Open that schema file and add a new element of customized section for testplan (I created an element named com.ibm.rqm.planning.editor.section.test for example). ![]() 4)copy the updated schema file back to the .dta zip file. Reopen it in RPE. ![]() |
![]()
Thanks for Chongyuan, however the solution provided here was not completed. The completed and tested solution was as follows.
Step 1. create the customized section in test plan template using RQM web UI. Step 2. Generate the test plan using the test plan created in Step 1. Step 3. Retrieving the customized section ID (generated by RQM automatically). Many handy tools can be used here. I am using Poster. Put the following URI enquiry: https://server:port/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/Project Area Name/testplan?fields=feed/entry/content/testplan[title='test plan name in Step 2']/(*)abbreviate=false The return messages will contain all the resources under the requested test plan. The bold font shows the internal ID for customized section "Environment" e. g. </com.ibm.rqm.planning.editor.section.dynamicSection_1381893903332 extensionDisplayName="Environment"> <div xmlns="http://www.w3.org/1999/xhtml">this is environment</div> Step 4. Edit XML schema file as described by Chong yuan. Make sure the "name" field is the same as the section ID. It does not matter with "documentation" field. And the "label" field will be the same as Section Name, which is "Environment". Note it is important to match the RQM internal ID, otherwise it will not work. Enjoy RPE. Comments Thanks Collin for providing the further details here.
The ID refers to "com.ibm.rqm.planning.editor.section.dynamicSection_1381893903332 ". Yes, the "name" field that was shown in above graph = com.ibm.rqm.planning.editor.section.test. The "name" field needs to exactly match the ID field obtained from the Poster return as I explained before. Hope it will help. Thanks Collin for the further clarification. It is very clear now.
|
![]() Publishing Test Plans' and Test Cases' custom sections were addressed in this thread, but what about Test Script custom sections? Where in the RPE QM schema XML should these be located? |
![]() I answered my own question! Here is my workflow:
|