Forum Discussion
Pru_PLC_Support
16 years agoOccasional Contributor
Hi Ole,
Both actually. It can load the project, but it omits the file that won't save (so it won't even load the previously saved version) and the same error message appears in the SOAP UI log.
I tried cloning the test case to another project and working on it there, which seemed fine, and it saved ok. But when cloned back to the original project it still won't save or load.
The only way I have been able to get the test case I want back into the correct project, is to create the project again from scratch. So all test suites were cloned to a new project and all project properties were set-up again.
This is now working fine in the new project, but we are still really concerned about why it happened as we lost a lot of work and have spent a day or so recovering it. We really don't want this to happen again but don't know how to avoid it.
Any ideas?
Thanks
Nicole
Both actually. It can load the project, but it omits the file that won't save (so it won't even load the previously saved version) and the same error message appears in the SOAP UI log.
I tried cloning the test case to another project and working on it there, which seemed fine, and it saved ok. But when cloned back to the original project it still won't save or load.
The only way I have been able to get the test case I want back into the correct project, is to create the project again from scratch. So all test suites were cloned to a new project and all project properties were set-up again.
This is now working fine in the new project, but we are still really concerned about why it happened as we lost a lot of work and have spent a day or so recovering it. We really don't want this to happen again but don't know how to avoid it.
Any ideas?
Thanks
Nicole