...
Load Test searches for a loadtest.config configuration file whenever it is started. If the file does not exist, Load Test and will create the file and print the location to the console. You will need to manually edit the configuration file if you want to change the Java runtime. For example:
| No Format |
|---|
atrujillo$user$ ./loadtest Found a new Parasoft Load Test installation. Parasoft Load Test will be configured. Using /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/bin/java Parasoft Load Test setup in /Users/atrujillo/Downloads/parasoft/soatest/9.10/Parasoft Load Test.app/Contents/MacOS/../../../Parasoft SOAtest.app/Contents/ParasoftSOAtest/eclipse/plugins/com.parasoft.ptest.libs.web_9.10.0.20161130/root completed successfully Starting Parasoft Load Test... |
...
Parasoft Load Test allows you to run your functional tests under increased loads. Parasoft Load Test repeatedly executes selected test suites with the specified number of virtual users or number of hits per second (hit rate).
...
| title | Web Load Testing |
|---|
...
.
...
The goal of load testing is to verify application/service performance and functionality under heavy load. It allows you the ability to run test suites in parallel with multiple threads and multiple users.
...
To thoroughly test performance, a functional test suite should be run under a variety of different scenarios to check how the different types of loads are handled. For example, the test could check functionality and response time under different degrees of load increases (sudden surges versus gradual ramp-ups) or different combinations of valid and invalid requests. If the load tests reveal unacceptable performance or functionality under load, the next step is to diagnose and repair the source of the bottleneck. Sometimes, the problem is caused by a fundamental algorithmic problem in the application, and the repair could require something as painful as an application redesign and rewrite. Other times, it is caused is caused by some part of the infrastructure (the Web server, the SOAP library, the database, and so forth). In these cases, fixing the problem might be as simple as changing a configuration or as complex as changing the architecture.
Because fixing performance problems sometimes demands significant application or system changes, it is best to start load testing as soon as possible. By starting early, you can diagnose and fix any fundamental problems before it is too late to do so without a major rewriting or rebuilding nightmare.
| Warning | ||
|---|---|---|
| ||
Parasoft does not recommend or condone performing load tests on public applications (including the applications that are referenced in the SOAtest tutorial). Please use it to load test only your own applications, or the parabank sample application used in the Load Test tutorial. |
How SOAtest Test Execution Differs in Load Test
Web Load Testing
Running hundreds or thousands of full browser instances is very resource intensive. Load Test replicates the network traffic generated by the browser sessions (such as API and page payload requests) rather than invoking multiple browsers and replaying user actions in them. This allows Load Test to simulate significantly more Virtual Users per machine. SOAtest allows you to automatically configure your browser-based functional tests for load testing. For details, see Preparing Web Functional Tests for Load Testing.
Test Suite Resource Sharing
If you want the tests in your Test Suite to reuse connections, sessions, or other test-specific resources (for example, OAuth 2.0 access tokens), you should enable "Tests run as a group" in in a Test Suite to which these tests belong (this option can be found on the Test Suite's Execution Options > Test Execution tab). This option allows each virtual user (VU) to run the entire Test Suite (Scenario), so when the VU acquires a test resource it will be able to reuse that resource. If "Tests are individually runnable" is is enabled instead, each VU will run one of the tests from the suite in isolation with no resource sharing between tests in a Test Suite.
Because fixing performance problems sometimes demands significant application or system changes, it is best to start load testing as soon as possible. By starting early, you can diagnose and fix any fundamental problems before it is too late to do so without a major rewriting or rebuilding nightmare.
...
| title | Test Your Own Applications--Not Public Applications! |
|---|
...
Traffic Stream Outputs
When Load Test executes tests from a SOAtest .tst file, tools attached to a test’s Traffic Stream output are not invoked. As a result, any processing implemented by tools attached to this output does not occur during load test execution.
Configuring Dependencies on External JAR files or Class Folders
...