It's all about the answers!

Ask a question

Start time not set when creating Test Result using OSLC v2 QM interface

Lars Ohlén (2566) | asked Aug 17 '12, 10:08 a.m.
When creating a new Test Result record via the OSLC v2 QM REST API the start time is not set.
The spec does not define any starttime attribute so there is no way to explicit set the value.
(The RQM UI shows starttime as N/A and in some cases 1970 January 1) 

We have used the RQM proprietary REST API to create the Test Result artifact and this correctly sets the starttime (as specified in the request), but a small side effect is that test script is not set (but is defined in the request).

As it looks right now we have to create the artifact using OSLC and then update the artifact with the RQM REST API  to have both starttime and script set.  

Is there any way to make just one request? Preferably just using OSLC.

Using RQM 4.0 


2 answers

permanent link
Pramod Chandoria (2.1k11220) | answered Aug 17 '12, 11:09 a.m.
Hi Lars,
I think this a RQM defect although QM specification does not mandate this property.
Please file a defect RQM New Defect

Lars Ohlén commented Aug 20 '12, 4:13 a.m.

Hi, Okey will do, but it will be two deftects: One for the OSCL QM API and one for the RQM REST API //Lars

permanent link
Paul Slauenwhite (8.4k12) | answered Aug 20 '12, 1:59 p.m.
Lars, this is a limitation in the OSLC QM V2 specification (see;up=#Resource_TestResult).  To work around this limitation, you will need to use the public RQM Reportable REST API ( to update the property (see  Note, the OSLC resource contains the RQM Reportable REST API URL in the dcterms:relation property.

I'm not clear on the issue with the test script with either API.

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.