Contributions
Re: SoapUI NG Pro 1.4.0 - JSON Response view removing decimal points
JSON can return just an integer, (20), it doesn't have to be (20.0). What they did with your fix was just added .0 to the end of everything, so that's why my assertions broke. Before this update, the raw response and the outline were returning (20)9 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.3KViews0likes1CommentRe: Switching between Projects tab and SoapUI NG tab can take several minutes to become responsive
Update: I changed some more settings in the ready-api.bat file and .vmoptions file. I adjusted the-XX:MaxHeapFreeRatio=40 to be-XX:MaxHeapFreeRatio=80 and it seems to be running better.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews1like0CommentsRe: SoapUI NG Pro 1.4.0 - JSON Response view removing decimal points
I'm running 1.5 maintenance build, and I have several hundred assertions setup to NOT include the decimal point. For example, I'm asserting the value "20" comes back for a dollar amount, but now the response is "20.0" so the assertion is failing (this is causing 300+ tests to show false failures). Could we please create a happy medium here and allow an option to display or remove unnecessary decimals? Thanks.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.3KViews0likes3CommentsRe: Switching between Projects tab and SoapUI NG tab can take several minutes to become responsive
The 1.5 nightly build did not resolve the issue, but I did notice our project has issues on the 1.5 release version that appear to be fixed in the nightly build version.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews0likes2CommentsRe: Switching between Projects tab and SoapUI NG tab can take several minutes to become responsive
Regarding version 1.5.1, I was referring to Tanya's response. I have not seeing one, but I'm assuming she meant the 1.5 maintenance builds. Yes, all computers used the same installer.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews0likes4CommentsRe: Switching between Projects tab and SoapUI NG tab can take several minutes to become responsive
I have not seen a 1.5.1 version to download, but we did install 1.4.1 on another laptop that is in the same city as our source control and switching between the tabs works fine. We are seeing the issue still on 3 different laptops that are in another city than our source control. This is the only difference between these setups that I can figure out at the moment.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.6KViews0likes6CommentsReady!API can become unresponsive for around a minute finishing a test case run
Sometimes after a test case run, Ready!API will stick on the last step in the test case and become unresponsive for a bit. Seems to be a problem after using both SoapUI NG tabs and the Projects tab.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes1CommentSwitching between Projects tab and SoapUI NG tab can take several minutes to become responsive
Issue is exactly as stated in the title. Ready!API does the spinning loading symbol up to several minutes trying to switch between these tabs. It makes it very annoying to use this tool as it eats up a lot of time just sitting here.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.7KViews0likes8CommentsRe: SoapNG Crashes Running All Test Suites At Project Level
I changed my .vmoptions file to include these values: -Xms256m -Xmx4096m and updated my ready-api.bat file with these values: set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx4096m -XX:MaxPermSize=256m -Dsoapui.properties=soapui.properties I understand my Xms values conflict in these files, but it appears to have resolved my issue, so I'm just going to leave it. We use a lot of groovy scripts in our tests, so we believe that could be part of the issue, so if anyone else reading this uses groovy scripts and sees performance issues, make sure you include this piece:-XX:MaxPermSize=256m I also adjusted a few test case log settings, but I don't think that was the issue because task manager shows that SoapNG is utilizing twice as much memory as before when it would crash (currently it's using 3.8GB of RAM) and it's running just fine after multiple full project runs. Thanks for offering the link that helped me set the correct memory values. One more thing to note: if your company has strict group permissionsset, you might need to run your file editor as an administrator to be able to edit the values above successfully.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes2CommentsRe: SoapNG Crashes Running All Test Suites At Project Level
I haven't changed any of the default settings regarding java heap size. As for consistency, 2 of our uses have to restart mutiple times a day. During regression test runs, I've had to restart multiple times to complete the run. Some of our test runs touch over 100 test suites and approximately 1000 unique tests, but within those tests I'm calling a lot of other tests I've setup as reusables to help create the proper pre-condition data. I will look into that article you shared and see if this helps, but I do believe the default settings should be able to handle more situations without resorting to force quitting the application.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews0likes3Comments