Releasing memory during intensive tests
I am running intensive tests of web services: - consuming 100 services - each service is tested by 100 XML requests. There is a test suite for each service and a test case inside the testsuite....
Forum Discussion
Rao, to your questions:
- Each WSDL has a single operation in most cases, i.e. my test project has 100 WSDLs.
- There are 300 test cases within project, 3 for each service.
- Project file size is 12 MB.
- The tests are now running sequentially (will execute them in paralell later on).
I like executing the tests from UI, but maybe I will use command line for these bulk tests.
Thank you KarelHusa for the details.
And another thing while using UI is to keep close ununsed projects.
UI can be used as any other IDE to develop design the tests and make sure they are working. Once it is done, command-line execution is the best way, helps to achieve automation / CI.
Looking at your reply, it is possible to split into multiple sub projects.
When a test suite is invoked in parallell mode, should be little cautious. Because, by default, soapui starts all the test cases at the same time, and that takes lot of system resources.
And another thing while using UI is to keep close ununsed projects.
UI can be used as any other IDE to develop design the tests and make sure they are working. Once it is done, command-line execution is the best way, helps to achieve automation / CI.
Looking at your reply, it is possible to split into multiple sub projects.
When a test suite is invoked in parallell mode, should be little cautious. Because, by default, soapui starts all the test cases at the same time, and that takes lot of system resources.
