Traceability with DOORS and RQM in RPE
Hello all.
Currently I am trying to replicate the use of getting requirements in DOORS associated with test cases in RQM. I am following: https://rpeactual.com/2015/11/20/traceability-with-doors-9-and-rqm/
I have gotten to the point where I am importing a REST v2 OSLC schema, however, RDF/TestCase/Relation is not an option in my imported schema.
I am using this base URL: https://server:<port>/qm/oslc_qm/catalog
I am authenticating with Basic Authentication and using the default query capability for TestCase.
The only option to select on the next page is oslc_qm:testCase http://open-services.net/ns/core#Resource
Shouldn't there be a relation option?
When I try to use form or OAuth authentication, I get two different error messages.
For form authentication, I get 'Response message: Unauthorized'.
For OAuth authentication, I get 'Can not access to the OAuthentication URL'.
Suggestions?
|
One answer
Dylan
A couple of suggestions and question. Why not ask on rpeactual as a comment to the post? I know it is monitored and updated frequently. Also, not sure why you have gotten to the point of importing the REST v2 OSLC schema. What part of the original post did not work for you? The author even had a DTA available. In addition, with 6.0.2 and RPE 2.1 it is now possible to eliminate some of the steps mentioned in this article which makes it easier. Just use the OSLC URL instead of the Reportable REST API. see this post: https://rpeactual.com/2016/07/03/oslc-api-and-pox-profile-simplifies-clm-traceability/ Comments
Dylan Mansour
commented Sep 06 '16, 10:37 a.m.
When I use the provided DTA, the report consistently fails. I don't think I am understanding the URL that is used to configure the QM_OSLC_TC data source at run time. |
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.