...
To help you collect network information and system performance data during load testing, Parasoft’s solution provides built-in and extensible monitoring capabilities. For instance, supported monitors include perfmon, SNMP, rstat, WebSphere, WebLogic, JBoss, Tomcat, and remote monitors. The solution's extensible and deployable monitoring framework allows you to extract just about any set of metrics from the system that is being subjected to load, graph and correlate those metrics visually to identify causes of performance issues, and apply expected quality of service policies on those metrics to get a high-level view of the system’s compliance with performance and reliability requirements.
...
The Parasoft SOAtest installer installs both Parasoft SOAtest and Parasoft Load Test.
Starting Load Test
...
You can open Load Test by clicking the Launch Parasoft Load Test toolbar button.
...
The console may not print the location of the configuration file after the first start up, but it is created in the following directory so you can edit it any time: <SOAVIRT_INSTALL>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root/
Licensing
The License Settings dialog appears the first time Load Test is launched. To access the License Settings dialog from within Load Test, go to File > License Settings.
The process for licensing Load Test varies slightly depending on your license type.
For node-locked licenses:
- Select Use node-locked license.
- Enter the license password provided to you by Parasoft in the Password field. Once the license is applied, the expiration date will populate automatically.
- Click OK.
For licenses served from License Server:
...
/
...
Load Testing SOAtest Functional Tests
...
The best way to start load testing is to have multiple test clients run the complete functional test, including request submissions and response verifications. When load testing ignores the functionality verification process and focuses solely on load-rate metrics, it risks overlooking critical flaws such as functionality problems that surface only under certain loads.
The best way to start load testing is to have multiple test clients run the complete functional test, including request submissions and response verifications. When load testing ignores the functionality verification process and focuses solely on load-rate metrics, it risks overlooking critical flaws such as functionality problems that surface only under certain loads.
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 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.
...
| 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. |
Migrating Tests from Earlier Generations of Parasoft SOAtest or WebKing
If you have load tests configured in SOAtest 5.5 or earlier, they can be imported and are fully supported. Load tests from Parasoft WebKing are also supported-- they should be opened in Parasoft SOAtest, then configured and validated for load testing as described in the SOAtest user’s guide.
Configuring Dependencies on External JAR files or Class Folders
...