It's all about the answers!

Ask a question

RQM REST API: testphases vs. iterations

Michael Haun (4921924) | asked Oct 02 '14, 11:14 a.m.
I'm having trouble finding information on testphases and iterations.  My main resource thus far has been:

My issue is when I pull the TC result and TS result information, each result maps to a "testphase id" in the XML.  So I pull the testphase information so I can get the testphase/iteration titles (I'm expecting that "testphases" are really RQM timeline Iterations).  I run the following:

 java -jar RQMUrlUtility.jar -command GET -user <user> -password <password> -filepath /tmp/output/testphase.xml -url " QA (New)/testphase?fields=feed/entry/content/testphase/(*)"

This gives me XML that looks like:

<entry xmlns="">
<content type="application/xml">
<ns4:testphase xmlns:ns4="http...
           <ns4:iteration href="" />

The problem is I will see multiple entries for "Swordfish_Test_Iteration" in the XML that each have a unique <ns6: identifier>, and this is what TC results and TS results map to (they have a "testphase id" field).  But, as implied, the <ns6: identifier> is NOT unique to an iteration.  What *IS* unique to a iteration is the <ns4: iteration href>. 

1) I don't see "iteration" as a property for testphase in the REST API documentation here:

Why is that?

2) It seems to map a TC result or TS result to a unique iteration I have to go TCR -> Testphase ID -> Iteration ID.  Is this the right approach?  If yes, why isn't there a more direct path for something so fundamental as mapping a TCR to a Iteration?

3) Can someone explain what a testphase is and what a iteration is?  And how they relate?

Please help me understand this.  This is preventing us from reporting results.

Kellen Bombardier commented Oct 02 '14, 12:17 p.m. | edited Oct 02 '14, 12:18 p.m.

I am seeing the same issue with a project we are working on. Can someone with information on these questions help out here?

Accepted answer

permanent link
Donald Nong (14.5k414) | answered Oct 02 '14, 11:58 p.m.
If you check the "Resources and their Supported Operations " table, you will see that the "testphase" resource is the Test Schedule of a Test Plan.
A test schedule is not the same as an iteration, but rather a combination of a test plan and an iteration (or iterations). This article explains it pretty well.
I'm not sure why "iteration" is not listed as a property of a "testphase" in the specification. From what I can see, the "iteration" property refers to an iteration (of a timeline) literally.
Michael Haun selected this answer as the correct answer

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.