It's all about the answers!

Ask a question

Error in RQM 3.0.1.1 on changing the state to approval


Kaushambi Singh (371310379) | asked Apr 21 '14, 8:47 a.m.

We are using CLM 3.0.1.1 . IN RQM, I am getting error while trying to approve a test case. The errror say "Test case cannot be approved until all its test scripts associated are approved due to artifact transition constraint." But the test script is already in approved state. What could be the possible reason for this error.

Please help with the answer

One answer



permanent link
Don Yang (7.7k21114139) | answered Apr 22 '14, 2:21 a.m.
We see some similar issue only when the scripts are duplicated from a deleted script and it occurs to specific testcase/testscript only. We used Poster add-on to retrieve testcase XML details to find out whether there is anything not obvious in UI which may contribute to the problem. An example REST API is:

https://localhost:9443/qm/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/project alias/testcase/urn:com.ibm.rqm:testcase:26
(any test case id applies to 26 placeholder)

Do you see the issue only in specific testcase+testscript or not?
If you remove testscript from test case and add it again and try, do you see any change?
Whether you try with supported browser(such as IE8) as v3011 is low and only some lower version of Firefox supports it.

From Manage Project Property, if you remove "Artifact State Transition Constraints > Approve Test Cases only when all referenced Test Scripts are approved.", will you be able to approve test case now? This is for testing purpose in case something unusual happens regardless this constraint.


Comments
Kaushambi Singh commented Apr 23 '14, 5:15 a.m.

Thanks for your reply. I see this issue in specifc test case and test script only.

I had tried this in IE 8.

From Manage property, I know we can do this but this would not be the right way.


Don Yang commented Apr 23 '14, 6:02 a.m.

I understand it is not right way to remove constraint from manage property. I was thinking to have a test in case you may have many similar artifacts having the issue.
Are you able to contact support to verify the database? I suspect something could be wrong in database which is causing the current issue to specific artifacts only.

If you run REST API against the specific TestCase, do you see anything abnormal?
If you duplicate the problem testcase and test script and associate them, do you have the same problem or not. If that works as expected, you may consider it as a practical workaround if further debug is not possible.

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.