It's all about the answers!

Ask a question

How to export a test script out of GC (Global Configuration) enabled RQM project area?

Natarajan Thirumeni (298529) | asked Oct 25 '18, 4:50 a.m.

Using a RESTClient (add on browsers) you're able to export a RQM artifacts (such as Test cases, test script) in a non GC project area. However, trying export same out of a GC - Global Configuration project return into an error messages or no content of QM artifacts. You're wondering why export does not work on GC enabled QM projects.

One answer

permanent link
Natarajan Thirumeni (298529) | answered Oct 25 '18, 5:08 a.m.
edited Oct 25 '18, 5:16 a.m.
Let me try to list of all required steps so it might be easier for someone who is trying to troubleshoot a customer issue where he / she want to export a customer's RQM script / test case for a local debugging purpose.

1. Install RESTClient (add on for browsers, available for Chrome / Fire Fox) and open REST client in a browser

2. Set Authentication
Basic Authentication : user name and password to access  RQM web application (Jazz user role is sufficient to perform GET)

3.  set headers (Configuration-Context is required for GC opted in PAs)
Accept: application/xml
OSLC-Core-Version: 2.0
Configuration-Context: <pick up URL from GC stream, click on Current Configuration, right click on GC stream and copy location. Example https://server/gc/configuration/2

4. Construct a REST URL for a test script (note, everything is tagged within <> needs to modified as per your environment)

_WpHpkfbNEeeOFKdOmMZnJQ - UUID of the project area. Alias name can be used too. To fetch UUID names, use https://server/qm/oslc_qm/catalog and search for Project Area name you're working with, example olsc tag, on this case, _WpHpkfbNEeeOFKdOmMZnJQ is UUID of PA.

<oslc:ServiceProvider ns12:type="oslc:ServiceProvider" rdf:about="https://server/qm/oslc_qm/contexts/_WpHpkfbNEeeOFKdOmMZnJQ/services.xml"><dcterms:title>JKEUsingConfig (Quality Management)</dcterms:title><dcterms:description>JKEUsingConfig (Quality Management)</dcterms:description><oslc:details rdf:resource="https://server/qm/process/project-areas/_WpHpkfbNEeeOFKdOmMZnJQ"/><ns9:consumerRegistry rdf:resource="https://server/qm/process/project-areas/_WpHpkfbNEeeOFKdOmMZnJQ/links"/></oslc:ServiceProvider>

278 - test script ID. Can be observed in web UI next to Script name (screen shot added to assist you)

6. Until this point all required parameters are set. In RETClient, you'll end something like below:

6. Click on GET in the RESTClient,
7. If all goes well, response code 200 is returned.
8. Go to response tab and copy and XML content (its a content of a Test Script)
9. Send out XML response to IBM support (added screen shot)

tips: to validate if the XML is all ok, you can try yourself to import this script using a construction -> import Test Script. it two step process. See screen shots below!

Vidya Malkarnekar commented Oct 25 '18, 11:31 a.m.

Looks good. You don't really need the header OSLC-Core-Version, but no harm if it's there too.

Your answer

Register or to post your answer.