Forum Discussion
jaydennis
14 years agoNew Contributor
This problem has not been solved. I downloaded the latest nightly builds for both SoapUI and LoadUI and checked out my soapUI project to make sure all the test cases ran properly. They ran fine under SoapUI and then I created a project under LoadUI to generate load against 4 test cases from the same SoapUI project and it ran fine there too. I saved the project and exited LoadUI. When I restarted LoadUI and attempted to reload the project, it gave me the project corruption error. I then removed the corrupted project and exited LoadUI and then restarted LoadUI to make sure everything was "clean". Once LoadUI was back up, I recreated the same project as I had before, referencing the same SoapUI project as before as well. I DID NOT run the test after it was created but instead simply saved the project and exited. I wanted to see if running the project could have been creating the problem or even updating the SoapUI project AFTER the LoadUI project had been created. My first attempt was to just reopen the LoadUI project without doing anything to the project in SoapUI and without having even run it in LoadUI. When I attempted to open the project in LoadUI, it gave me the corrupted project error. Again, all I did was create the project and save it, close LoadUI, restart LoadUI, and then try to reopen the project I just created. I sent an email to the support email address along with the corrupted project in a zip file for analysis. This has become a very frustrating bug and I hope someone is looking into the cause and a resolution.