Page History

This topic explains how to perform load testing.

In this section:

...

• Customizing Load Test Parameters
• Running Load Tests on Remote Machines
• Using Monitors

Creating Load Tests for SOAtest Functional Tests

...

1. In the initial wizard panel, specify which .tst file contains the SOAtest tests you want to use for load testing, then click Next.
2. If an existing load test configuration is detected in the specified .tst file, do one of the following:
   • To use the existing configuration, select Existing Configuration and click Finish.
   • To create a new configuration, select New Configuration and click Next.
3. In the VU Profiles panel (for SOAtest components only), select the test suites you want to use, then click Next.
   • Each selected test suite will be assigned to a different virtual user profile.
4. In the Schedule and Distribution panel, customize the available options as needed, then click Next.
   • Controlled Parameter: If you want Load Test to try to achieve the specified virtual user quantities (and possibly vary the number of hits per second in the process), choose Number of Users. If you want Load Test to try to achieve the specified hit rates by varying the number of virtual users as needed, choose Hits per Second, Hits per Minute, Hits per Hour, or Hits per Day.
   • Schedule: Enter new values in the Duration fields. Days are limited to 30, hours are limited to 23, minutes are limited to 59, and seconds are limited to 59.
   • Distribution: Select the type of distribution from the following options:
     • The Linear Increase scenario simulates a load that increases linearly over time. This is useful for capacity testing, which helps you determine scalability.
     • The Steady Load scenario simulates a steady load of users over time. This is useful for endurance testing, which helps you determine whether performance degrades over time.
     • The Bell scenario simulates the typical daily user distribution (starts at the lowest point immediately after midnight, rises gradually in the morning, peaks towards the middle of the day, declines gradually in the afternoon, then returns to the lowest point at the end of the day). This is useful for expected usage testing, which determines whether performance problems occur with normal load patterns.
     • The Buffer Test scenario simulates a variable load over time. This helps you determine whether resources are released when the load decreases. It also helps you determine whether overall performance degrades over time.
5. In the Performance Monitors panel, configure performance monitors as needed, then click Next.
   • For more information on performance monitors, see Adding Built-In Monitors.
6. In the Quality of Service panel, customize the metrics as needed, then click Next.
   • 100% Success: The measured percent of succeeding request messages must be exactly 100%.
   • Fast Hit Rate: The throughput achieved during the load test must be above the defined level.
   • Low Server Time: Verifies that the average server time is below the specified threshold.
   • No Failures: The total number of failures occurring during the load test must be zero.
   • Low Execution Time: Verifies that the average execution time is below the specified threshold.
     For more information on Quality of Service, see Customizing QoS Metrics for Scenarios.
7. In the Slave Machines the Agent (Remote Machines) panel, configure remote machines as needed, then click Next.
   • You can add or remove remote machines, as well as select High Throughput to disable test response verification.
   • For more information on slava machines, see Customizing QoS Metrics for Scenarios.
8. In the Other Options panel, customize options as needed, then click Finish.
   • Start Load Test immediately: Select this option to immediately begin load testing once the Finish button is clicked in the Load Test Configuration wizard.
   • Record graph data and error details: Select this option to have Load Test create a detailed scenario report after the completion of a load test. For more information on detailed reports, see Detailed Reports. After enabling Record graph data and error details the following options are available:
     • Record first: Enable and enter a number in the text field to record the first number of error details you specify. This option is useful in preventing the detailed report files to grow to unmanageable sizes if a large number of errors are produced. By default, the first 300 error details are recorded.
     • Record all: Enable to record all error details in the detailed report.
     • Record individual hits: Enable to record individual hits and to have Load Test create a histogram as part of the detailed report after completion of a load test. You will also have the option to display individual hits in graphical and table forms within the Detailed report.

...

If Load Test encounters errors during test execution (for example, if it cannot start testing on a remote machine because that machine is not running Load Test ServerAgent), it will display an orange exclamation point icon in the status bar. 

...