Tag Info

New answers tagged

2

First you need to define what the "breaking point" is. There are a number of possibilities. The obvious problem would be if the web server itself crashes and stops responding, but there are a number of problems that can occur well before that point that in most cases would still be considered "broken". Some other problems that could tell you your ...


0

To determine the breaking point of you application increase the thread count gradually with each test run. At present you have it as 10. Now try testing with 20, then 50 in third iteration. Now suppose you find out that you application broke at 50 threads, then reduce the thread count to 40 and run the test again. Let's say your application works fine with ...


0

Is the slowness on the app a result of the sum of these 3 requests: around 7000ms ~ equal 7s? (It is still way much lower than 17s on real device) Yes That is most likely the cause of your issue. The application likely catches and retries when it times out which will give you these very long times. It sounds like there is some severe issues, most likely in ...


1

As far as I'm aware data export and reporting you're looking for is available in Pro version of SoapUI. I would recommend developing your tests using SoapUI and using Apache JMeter for load testing as it's capable of sending SOAP requests, performing assertions and correlation and has powerful and flexibly configurable reporting system. References: ...


1

I am unaware of any standard definition for "Software Reliability Report". And an internet search doesn't show anything either. So you have 2 options: Ask management what they want in the report, or if they don't know, ask them what the report is for and use your best judgement. Make something up. List of known defects, supported usage scenarios, ...



Top 50 recent answers are included