Cannot create test scripts on RQM 6.0.2
![]()
Hi All,
I have upgraded RQM 6.0.1 to 6.0.2 and haven't applied any fixpack.
My problem is: I cannot saving my test scripts, and ended up with error message.
Below is the error messages from RQM:
"Unable to save test scripts"
"Validation error for item: type = ExecutionElement2, itemId =[UUID_0SN-MH5LEeaigvKWNLaMyQ]
"Required String property must not be empty: summary"
Need your assistance, to fix this problem.
Thanks
|
2 answers
![]() Hi All did you manage to find a solution for this Problem? Since today we are facing the same issue with RQM 6.0.3 iFix006. Some of the Test Scripts cannot be edited and saved any more. Also a simple state transition (Draft -> Under Review) without any modification is not possible.
Error message:
Unable to save Test Script
Validation errors for item: type = ExecutionElement2, itemId = [UUID _gUoOcT4NEea3-PKofvMcuA] Required String property must not be empty: summary
The summary section is empty. Any idea how to overcome this?
Thanks and best Regards
|
![]() Hi, Gabor
|
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.
Comments
Hi, Prussian
1. Do you see all those messages when saving test scripts?
2. whether any test script save will end up with same errors?
3. whether test script summary is over 250 characters?
4. is it happening in any browser?
5. what is the output
https://server:port/qm_context_root/resource/itemOid/com.ibm.rqm.planning.ExecutionElement2/_0SN-MH5LEeaigvKWNLaMyQ
from a web browser?
(server:port and qm_context_root should be matching to your environment)
I can't tell from the error "Attempt to fetch config aware type with no configuration set"
if there is anything to do configuration management. If this is a configuration enabled project, you may check with other project and see if you see similar problem.
I don't find any reported problem in v602 which has the same errors in this post. In a general approach, you may try to apply ifix on v602 first and see how it works.
Obviously if ifix does not help, further trace is required to find out more, if you know how to use firebug, you can reproduce the issue and see if the firebug can reveal anything more. if you can contact support, there is some further trace they can enable for qm.log for investigation.
Donal, the condition is like below:
I don't see the link between the error and RS staying at 6.0.1. You can upgrade RS now as I understand because JTS is now at 6.0.2.