Unable to edit a Test Case
Hi I am wondering if anyone has any ideas on the following:
I test case was created whilst running a particular workflow, this at the end locked the Test Case.
Subsequently the same workflow has been amended and this has caused the Test Case to try and resave itself under the first state of the amended workflow. However the problem is that you are unable to save the change as it advises that the Test Case is locked, and you cannot unlock the Test Case as it says you have unsaved changes.
You are left in a loop that I cannot see how you can break.
I know I can duplicate the Test Case, but this then means I loose the execution history from the original, so would rather try and fix if there is a way.
Can anyone advise?
I test case was created whilst running a particular workflow, this at the end locked the Test Case.
Subsequently the same workflow has been amended and this has caused the Test Case to try and resave itself under the first state of the amended workflow. However the problem is that you are unable to save the change as it advises that the Test Case is locked, and you cannot unlock the Test Case as it says you have unsaved changes.
You are left in a loop that I cannot see how you can break.
I know I can duplicate the Test Case, but this then means I loose the execution history from the original, so would rather try and fix if there is a way.
Can anyone advise?
Accepted answer
I suspect that the change of the workflow makes the state of the said test case invalid. If it is true, the only way out is to put this state back to the workflow so that you can move the state to a valid state in the target workflow. To verify this, simply load the test case in the RQM web client, and you may see a message "artifact's state has been updated". Click on "show details" and you may see "current state 'xxxx' is not valid in the current workflow. The artifact's state has been set to the current workflow's initial state 'yyyy'".
Comments
1 vote