Forum Discussion
Dragon
13 years agoNew Contributor
Just a quick update.
The problem seems real. I uninstalled loadUI 2.5.0 and reinstalled loadUI 2.1.2. After loading the project in loadUI 2.1.2, all the soapUI runners had the same test case, indicating 2.5.0 did change the project.
So, I updated my project file from my svn so that I got back the correct file. To prove it correct, I loaded the updated project file in 2.1.2 and it showed the correct soapUI runners.
Then, I repeated the steps in my last post (uninstall 2.1.2, install 2.5.0, and load the project in 2.5.0). The soapUI runners are changed again, showing they all have the same test case.
The problem seems real. I uninstalled loadUI 2.5.0 and reinstalled loadUI 2.1.2. After loading the project in loadUI 2.1.2, all the soapUI runners had the same test case, indicating 2.5.0 did change the project.
So, I updated my project file from my svn so that I got back the correct file. To prove it correct, I loaded the updated project file in 2.1.2 and it showed the correct soapUI runners.
Then, I repeated the steps in my last post (uninstall 2.1.2, install 2.5.0, and load the project in 2.5.0). The soapUI runners are changed again, showing they all have the same test case.