It's all about the answers!

Ask a question

Not able to get testcase details using Reportable Rest API to GET all test cases filtered by specific custom attribute


Rakhi Raikwar (11) | asked Oct 14 '22, 4:55 a.m.

Hello,


I am trying to use Reportable Rest API to GET all test cases filtered by specific custom attribute. For example, name of custom attribute is 'ATETestNr'.

I am giving below query: -


headers added:
Accept:application/rdf+xml
Content-Type:application/rdf+xml

Total 19 testcases available in the stream. I am getting the output of 10 testcases aligned with custom attribute correctly but when I am trying to get details of next page rel="next" the data It is referring is from different stream. Also not getting the data of stream I mentioned in my rest call.

Could you please let me know how I can get data of next page. Let me know if any mistake I am doing from my end.

Regards,
Rakhi


Comments
Ian Barnard commented Oct 14 '22, 5:15 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

What does the link for the next page look like - can you edit it (obfuscate the hostname if you want to) into your question? You aren't modifying it in any way, are you?


One answer



permanent link
Ian Barnard (2.1k613) | answered Oct 17 '22, 4:26 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 In your original request are the query parameter values URL-encoded? The actual URL used should look like:


https://SERVER:PORT/qm/service/com.ibm.rqm.integration.service.IIntegrationService/resources/_6Cf2BOCaEeuaurObCHGwiA/testcase?fields=feed%2Fentry%2Fcontent%2Ftestcase%5BcustomAttributes%2FcustomAttribute%2Fname%3D'ATETestNr'%5D%2F*&oslc_config.context=_DxGdfS0REe2HB9Qt1cG-9Q

The next page URL uses (as expected) the same configuration you specified in the original request - are you certain this is the configuration you're looking at to check for the 19 test cases?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.