Different types of Load testing
Hi Can anybody help me to find out the different types of Load testing that can be executed using Soap UI? For ex: Soak test, Stress test, Failover test, volume test. Regards Patrick pat...
Forum Discussion
NiclasReimertz
Staff
StaffHi Patrick,
REALLY interesting question. No, there isn't any good material about this and we should add it to the documentation.
Some quick thoughts:
Soak testing.
Easy, soak testing is just running tests over a long time. What you need to be aware of is how to tweak soapUI to conserve memory while running the tests. Admittedly, soapUI CAN use up memory if not done right. Look at Ole's blog post here: http://www.eviware.com/blogs/oleblog/?p=17
Stress Testing
Yep. Love this one. Since it's so easy creating LoadTests from a functional tests, do this: create one with any strategy like Simple and have it running as a reference and then create a second Load Test with a burst strategy and run that too. The neat trick is running two or more LoadTests at the same time. Just remember this, the more aggressive your tests are, the more resources the tests will use, especially when it comes to socket usage. In some Windows versions it's pretty easy to use up all sockets (I'm not knocking on windows...) so you might have some configuring to do.
Failover Testing
Failover testing isn't done by the tool itself, is it? Just run a load test, go into the server room and disconnect a web server and see how the failover set up works.
Volume Testing
Volume testing is really usable, there are two classic volume tests; large databases and large payloads. Large databases is not something that can be done in soapUI since we can't modify the database, but take a look at soapUI DataPro http://www.eviware.com/index.php?option=com_content&task=view&id=142&Itemid=14. Large payloads is easy, just create a functional test with large payloads and then run it as a LoadTest.
As you see, there's a lot to write about in the documentation, but I want to encourage you to look at the stuff we have.http://www.soapui.org/userguide/loadtest/index.html
/niclas
eviware.com
REALLY interesting question. No, there isn't any good material about this and we should add it to the documentation.
Some quick thoughts:
Soak testing.
Easy, soak testing is just running tests over a long time. What you need to be aware of is how to tweak soapUI to conserve memory while running the tests. Admittedly, soapUI CAN use up memory if not done right. Look at Ole's blog post here: http://www.eviware.com/blogs/oleblog/?p=17
Stress Testing
Yep. Love this one. Since it's so easy creating LoadTests from a functional tests, do this: create one with any strategy like Simple and have it running as a reference and then create a second Load Test with a burst strategy and run that too. The neat trick is running two or more LoadTests at the same time. Just remember this, the more aggressive your tests are, the more resources the tests will use, especially when it comes to socket usage. In some Windows versions it's pretty easy to use up all sockets (I'm not knocking on windows...) so you might have some configuring to do.
Failover Testing
Failover testing isn't done by the tool itself, is it? Just run a load test, go into the server room and disconnect a web server and see how the failover set up works.
Volume Testing
Volume testing is really usable, there are two classic volume tests; large databases and large payloads. Large databases is not something that can be done in soapUI since we can't modify the database, but take a look at soapUI DataPro http://www.eviware.com/index.php?option=com_content&task=view&id=142&Itemid=14. Large payloads is easy, just create a functional test with large payloads and then run it as a LoadTest.
As you see, there's a lot to write about in the documentation, but I want to encourage you to look at the stuff we have.http://www.soapui.org/userguide/loadtest/index.html
/niclas
eviware.com