It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,962
×10,913
×476

question asked: Jan 09 '15, 2:07 p.m.
question was seen: 4,408 times
last updated: Jan 12 '15, 12:46 p.m.

Related questions

problem with test plan that has a test case href with a non-ascii character

0
John McMeeking (6●3●3) | asked Jan 09 '15, 2:07 p.m.
I have a tool that is trying to work with a strange test case URI returned as part of a test plan XML document.

The testcase href contains a non-ASCII character represented in the XML document as  

    <ns0:testcase href="https://jazz-server:11443/jazz/service/com.ibm.rqm.integration.service.IIntegrationService/resources/My+Project/testcase/blah_&#160;_blah" />

I believe the corresponding URI should be:
https://jazz-server:11443/jazz/service/com.ibm.rqm.integration.service.IIntegrationService/resources/My+Project/testcase/blah_%a0_blah

But that URI gets me a 404 error.

How can I deal with that URL? Can I change my REST GET request to return a different URL in the test plan document?  I see a hrefs with a mix of internal and external IDs.  Can I get these as internal IDs?

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Paul Slauenwhite (8.4k●1●2) | answered Jan 12 '15, 10:16 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
All URI-reserved characters (see RFC 2396) except the '/' character in an external ID MUST be URL encoded in GET/PUT requests (see https://jazz.net/wiki/bin/view/Main/RqmApi#External_ID). 
Comments
John McMeeking commented Jan 12 '15, 12:02 p.m.
Clarifying my original post (and squeezing into character limit):

1)  The test plan XML document return to me by RQM contains an href that used an external ID style URL.  The XML document contained an embedded "# & 160 ;" (no spaces - original post clobbered that sequence).  The entire external ID portion of the href was:
Solution_Story_191458_deploy_vm_with_different_AZ_nodify_default_schedule_zone_in_nova.conf_to_AZ_1_and_deploy & # 160 ;_nova_AZ_2
I don't think that has any other special characters.

2)  Python XML library extracted the href as a string with an embedded byte, \a0, which urllib2 rejected as containing a non-ascii character.

3) I URL-encoded the URL, replacing the \a0 byte with the string %a0.
Server returns 404 error.  So it seems the URL-encoded URL is not usable either.

Back to my original questions.
Paul Slauenwhite commented Jan 12 '15, 12:46 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

John, can you trying using HTTP Requester or Poster to GET the feed of test cases and the test case in question?  Just log in to RQM using Firefox and GET the test case feed/resource from HTTP Requester or Poster with the following header:

Accept = application/xml

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.