Forum Discussion
I think the best way to troubleshoot this would be to install SoapUI 5.5.0 on another machine with the GUI capability and try running the same tests. Obviously there's something wrong, but running it in ReadyAPI will not evidence the problem. To make it easier to troubleshoot, can you try installing SoapUI 5.5.0 on a machine and run the tests through the GUI there? Might evidence something that's easily missed in the logs.
- richie6 years agoCommunity Hero
Hey msiadak,
Sorry - I obviously wasn't clear (again! :))
That's exactly what I've been doing - I have ReadyAPI! on my laptop and I installed SoapUI (free) on my colleague's laptop.
I've been switching between executing the test in ReadyAPI! on my machine and executing the same project within SoapUI on his machine all day, comparing the two.
Appreciate the advice!
rich
- nmrao6 years agoChampion Level 3
Sorry, I couldn't go thru entire post.
If the project is not using any ReadyAPI features, better to design the tests in free edition which is fair and simple to do instead of doing what went wrong.- richie6 years agoCommunity HeroHey Rao,
Yeah that did cross my mind, however creating in soapui free is unfeasible due to following:
The project is relatively large and would take 3 or 4 weeks to create.
Only 12 tests out of a project containing 800 are problematic.
Thanks
Rich
Related Content
- 3 years ago