Contributions
Re: MEMORY LEAKS, non suitable for load tests!
HiMFagerlind, yes, Ready!API v1.6.0 also can you please explain what is "Customer care team". I was not able to find access to any public issue tracker to submit the report. MFagerlind wrote: We recently proved to a very happy customer that we could generate 100,000 virtual users. the number of virtual users actually says nothing about actual test performanceutil there is info about their scenario. What kind of requests and how often... MFagerlind wrote: Maybe there's a problem with running load tests with huge Groovy setup scripts. As Imentioned in the initial post (and this can be seen in the attached project), the "hudge" groovy script included only one line with "//" (comment) and nothing else. Thanks.9 years agoPlace ReadyAPI QuestionsReadyAPI Questions4KViews0likes1CommentMEMORY LEAKS, non suitable for load tests!
Hi All, does anyone use this tool for load/performance testing inREALITY? I reallywill be gladto hearnot that marketing bull**bleep** but real success story... We have implemented quite a lot of functional tests around the SoapUI, even free version covers most of our needs. But it seems that now we came to the line to throw it away (or at least use some other product for load tests). The idea was quite simple - use some of the functional tests as buildingbricks forloadtests. Yes, I know that this is not always an optimal solution (quite expensive to carry on all the asserts as in functional tests) but still, this should be possible as we have enough of hardware to emulate required number of VU, I thought... We decided to evaluate commercial version of ReadyAPI/LoadUI(I would say it costs quite a lot but we CAN offer it if it really works and solves our needs). But evaluation results really disappointed us. Please find attached ReadyAPI project. Observations: - On localhost I have Tomcat running and serving requests to static .xml file (file size is approx 1 kB). - with 10 VUs and zero wait time LoadUI is capable to perform approx 1000 requests per second to this file (while JMeter on the same hardware makes 1800+), ok,acceptable. - in realitywe are going to use our existing functional testcases so we test this scenario using one Run Testcase step. this drops TPS to 800. - thenadd "enormous" groovy Setup script consisting of one "//" (comment). TPS drops to < 200 ! - less than a minute of such run and LoadUI occupies all available heap and dies. Soeventhis simple scenario is failed! What to say about complex test scenarios. Is SmartBear able to understand thatwe can't use buggy tools for QA. Why not to invest some time/money in bugfixing rather than adding new features? Whoneeds Cloud Testing if memory is leaking during test! Regards, multiware9 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.1KViews0likes6CommentsRe: Migrating a project from SoapUI 5.0.0 to PRO
it seems the same issue that we faced withSoapUI 5.1.3 https://community.smartbear.com/t5/SoapUI-Open-Source/SoapUI-5-1-3-mockRequest-getRequest-getParameter-quot-paramName/td-p/99876/jump-to/first-unread-message very strange, that there is still no response in this thread from SmartBear, especially for the issue withsuch topic "Migrating a project from SoapUI 5.0.0 to PRO" ;-)9 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes1CommentSoapUI 5.1.3, mockRequest.getRequest().getParameter("paramName") - returns null for POST request
Hi All, While trying to extract parameters in "MockeService/MockAction/Dispatch script"from POST request we faced the following issue: POST with parameters ecoded: application/x-www-form-urlencoded mockRequest.getRequest().getParameter("paramName") - returns null parametersMap() is empty the same code inSoapUI 5.0.0 works correctly, Any ideas? or ways to bypass this issue?5.1KViews0likes2CommentsREST, MockAction, using template parameters in ResourcePath
Hi, I'm working on the REST service mock and need a way to process URIs with template parameters, something like this: http://localhost:8080/edit/{id} I need to be able to: - process /edit/1 .... /edit/999 with the same MockAction, does MockAction support any kind of "parameterized" request paths? - extract {id} parameter from the uri in order to use this parameter in scripts. is this possible with SoapUI?4.1KViews1like6Comments