Is it possible to update test script step results via OSLC QM API with requirement links in version 7.0.2?
Now, my question is: does version 7.0.2 support the update of requirement links in test script step of test case results?
8 answers
Be as clear and specific as you can when creating your support case. The initial support engineering you work with may not have any development skills or know the API, so give them the exact XML you are PUTting or POSTting to the server. Your goal is to make it as easy as possible for Support to reproduce the issue. Once they can reproduce the issue, they can escalate to Development.
It looks like the child story 180460: Story: Update test script step result using OSLC API for remaining properties for create and update operation says that it was complete in 7.0 and included the oslc_qm:validatesRequirement link type. I have not tried it in 7.0.2.
Comments
I'm not aware of anything else required. I suggest you submit a defect against ETM. 180460: Story: Update test script step result using OSLC API for remaining properties for create and update operation indicates that should have been implemented in 7.0.
I've no permission to add a defect ticket:
Contact support - they should be able to do so for you.
I've tried to post the following content as defect:
Build ID and/or link: I20220722_0910
OS: Windows Server
DB vendor and version: n/a
Browser vendor and browser version: n/a because using OSLC REST API
Is this problem reproduced only on a CM enabled project area? n/a
Problem Description:
Update test script step results via OSLC QM API with requirement links (oslc_qm:validatesRequirement) does not work.
Steps to reproduce:
1. use GET request via OSLC API to read an exsiting ExecutionElementResult object,
Expected behavior:
the ExecutionElementResult shall contain the added oslc_qm:validatesRequirement property,
Actual behavior:
No changes on ExecutionElementResult detected, so the oslc_qm:validatesRequirement isn't added to ExecutionElementResult object.
Work around:
No work around found for this issue.
Some guidelines when creating a defect:
- Add as many details as you can.
- Attach any relevant files. Logs are always welcome, see: https://jazz.net/help-dev/clm/topic/com.ibm.rational.test.qm.doc/topics/c_rqm_logfiles_loc.html for more information.
- Attach any relevant screen captures(required). Screen captures are an excellent way to help on describing your problem.
Some remarks,
Comments
As you suggested, I tried deleting one requirement link from an ExecutionElementResult object that contains two req. links. Unfortunately that didn't work either. Your reference above refers to DNG, I think that cannot be compared to the behavior in RQM.
A link between two applications might only be stored in one application. Even if the link shows in both XML's, it might have to be deleted in a specific application.
You need to understand where the link is stored (likely ETM as DNG tries to make the other apps responsible) and update the item where it is stored. It might be stored in the ETM and not the DNG item. Just my best guess from previous discussions.
My problem is not deleting requirement links. My main problem is that existing requirements links in a test script step definition are not included in the result when I use the Reportable REST API to generate test results. Unfortunately, when I try to add the missing links via the OSLC API, it doesn't work. I just want the links to appear in the test script step result as defined in the test script step. It also works when generating results via the GUI. I simply want the same behavior as with the GUI.
I can only point out pattern I have seen. I don't have experience with the ETM reportable REST API and do not have an answer to your question.
- To update OSLC links in RQM, you have to use the OSLC API.
- Are you using Lyo to do OSLC development? If not, please do. It will make your life a lot easier: https://oslc.github.io/developing-oslc-applications/eclipse_lyo/eclipse-lyo.html
- Are you able to link a test case to a requirement? If you can, then you know your problem is script step specific. If you can't, then you have a more fundamental issue going on in how you are creating the links.
Comments
We have designed our own java toolbox to handle the REST APIs of DNG and RQM. Yes, we have been using this use case for quite some time. First, we create a test case object via Reportable REST API and do in a second step an update with requirement links with the OSLC API - it works well.
