krstn123
14 years agoNew Contributor
What settings do you use to make SoapUI usable in long run?
Hi,
we are facing some extraordinary issues with SoapUI, and since we've tested it on many computers, multiple systems [win xp, win 7, snow leopard, lion] I don't think it's possible no one else is facing them.
1. After some time editor windows will fail to open - yeah.. just like that. you double click on a test case or anything else and it will not open - solution: restart soapui
2. Groovy script editor fails to undo/redo on mac [not tested on windows though] - Cmd+z will remove everything from the editor window. Yup... just like that. No way to undo. Solution: don't even think about saving your project and restart soapui. If you will save your project, you better pray for a good version control system or you're lost.
3. Soapui sometimes sends two requests instead of one. Just like that. I can see a request "running" but in the meantime soapui sends another request [we encounter it all the time when debugging our webapp and sometimes when running test cases - some database concurrency errors etc. ] - no solution to this [I've found a tip on this forum about some preauthentication tick in options, but it changes nothing].
4. Soapui becomes unresponsive after some time of working with it. Menus open without entries in them [just a blank popup menu], on the project tree, when opening a branch we can see empty space instead of test steps etc. Solution: restart soapui.
5. We are unable to stop load tests/tests. We hit stop but they go on in the background. Solution: Kill soapui [exit won't do - java process stays in the background].
These are the most common issues we face. Unfortunately they occur very often.
Since I know this tool is used in many places I doubt there's no way to deal with these issues. Could you please spare a tip or two on how to get rid of them?
Thanks,
Krystian
we are facing some extraordinary issues with SoapUI, and since we've tested it on many computers, multiple systems [win xp, win 7, snow leopard, lion] I don't think it's possible no one else is facing them.
1. After some time editor windows will fail to open - yeah.. just like that. you double click on a test case or anything else and it will not open - solution: restart soapui
2. Groovy script editor fails to undo/redo on mac [not tested on windows though] - Cmd+z will remove everything from the editor window. Yup... just like that. No way to undo. Solution: don't even think about saving your project and restart soapui. If you will save your project, you better pray for a good version control system or you're lost.
3. Soapui sometimes sends two requests instead of one. Just like that. I can see a request "running" but in the meantime soapui sends another request [we encounter it all the time when debugging our webapp and sometimes when running test cases - some database concurrency errors etc. ] - no solution to this [I've found a tip on this forum about some preauthentication tick in options, but it changes nothing].
4. Soapui becomes unresponsive after some time of working with it. Menus open without entries in them [just a blank popup menu], on the project tree, when opening a branch we can see empty space instead of test steps etc. Solution: restart soapui.
5. We are unable to stop load tests/tests. We hit stop but they go on in the background. Solution: Kill soapui [exit won't do - java process stays in the background].
These are the most common issues we face. Unfortunately they occur very often.
Since I know this tool is used in many places I doubt there's no way to deal with these issues. Could you please spare a tip or two on how to get rid of them?
Thanks,
Krystian