RQMURLUtility: Error retriving list of Test Case
I'm tring to use RQMUrlUtility in order to have a complete list of Test Cases to reat the ID.
In my project I've 88 TC,
I use the following command:
java -jar RQMUrlUtility.jar -command GET -user oreste -password oreste -filepath D:\Lavoro\ListaTestCase.xml -url https://10.6.11.30:9443/jazz/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/AREA+SPAG-TFA/testcase
The list that I obtain only contain 50 TC.
I tryed to download several TC not in the list and I've no problem.
Any suggestion? :?:
In my project I've 88 TC,
I use the following command:
java -jar RQMUrlUtility.jar -command GET -user oreste -password oreste -filepath D:\Lavoro\ListaTestCase.xml -url https://10.6.11.30:9443/jazz/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/AREA+SPAG-TFA/testcase
The list that I obtain only contain 50 TC.
I tryed to download several TC not in the list and I've no problem.
Any suggestion? :?:
12 answers
When you do a GET for a list of items RQM is purposely limiting how many items get returned in the list. By default it will return 50 items. This is the strategy RQM uses to deal with repositories containing a very large number of items. Near the top of the XML that gets returned are some elements named "link". These elements contain a relationship attributed named "rel". If there is a link element with a "next" relation, then that's the href you use to get the next page of items. So if you rerun the RQMUrlUtility with the href from the "next" link element, then you would GET the next set of test cases. In your case that would be cases 51-88.
One gotcha to be aware of is that the URL in the link element was encoded to be XML friendly. Most notably is that '&' was encoded to be "&". You'll need to reverse that in order for your next GET to work. So simply replace all "&" with '&' in the href that you pulled out of the link element and you should be good to go.
One gotcha to be aware of is that the URL in the link element was encoded to be XML friendly. Most notably is that '&' was encoded to be "&". You'll need to reverse that in order for your next GET to work. So simply replace all "&" with '&' in the href that you pulled out of the link element and you should be good to go.
Kurtis, I tried the above idea and I get the same page 1-50 TS only. What might be the problem? href for page 2 below. Thanks
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=1
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=1
When you do a GET for a list of items RQM is purposely limiting how many items get returned in the list. By default it will return 50 items. This is the strategy RQM uses to deal with repositories containing a very large number of items. Near the top of the XML that gets returned are some elements named "link". These elements contain a relationship attributed named "rel". If there is a link element with a "next" relation, then that's the href you use to get the next page of items. So if you rerun the RQMUrlUtility with the href from the "next" link element, then you would GET the next set of test cases. In your case that would be cases 51-88.
One gotcha to be aware of is that the URL in the link element was encoded to be XML friendly. Most notably is that '&' was encoded to be "&". You'll need to reverse that in order for your next GET to work. So simply replace all "&" with '&' in the href that you pulled out of the link element and you should be good to go.
Helllo Paules
The href I posted is of "next" attribute only. I am guess it is not working because we have 3.0.1 RQM and not 3.0.1.1. Is that correct?
Thanks
Rajesh
The href I posted is of "next" attribute only. I am guess it is not working because we have 3.0.1 RQM and not 3.0.1.1. Is that correct?
Thanks
Rajesh
See https://jazz.net/wiki/bin/view/Main/RqmApi#Feeds.
See the href=<next> attribute on the link element with the rel="next" attribute.
Sure here it is Paul.
Alternate:
https://rqmweb.hq.tellabs.com:9445/qm/web/console/
Self: https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=0
Next:
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=1
last:
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=21
Thanks
Alternate:
https://rqmweb.hq.tellabs.com:9445/qm/web/console/
Self: https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=0
Next:
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=1
last:
https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=21
Thanks
These URLs look correct (except for https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/53532). Does https://rqmweb.hq.tellabs.com:9445/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/MSO+%28Quality+Management%29/remotescript/?token=_3TKfce_gEeCY2ab17Pqhfg&page=1 return the same page (and self/next links)?
page 1of 1 pagesof 2 pages