LoadView Goal-Based Load Test is a smart testing tool that provides testing against a target number of transactions, automatically adjusting all the necessary test parameters, such as user load and test scenario.

A goal-based load type is useful when you have already identified the limiting level of your required throughput and need to ensure that your performance goal is met.

To calculate your goal throughput, see How to find your Transaction Goal.

How it works

Based on the provided transaction goal and device response time, our platform recommends a starting and a maximum number of users, as well as the load test duration. When the test starts, it goes through several cycles of measurements and load adjustment stages. During these measurements, the number of transactions is being calculated and based on the results, the load is either increased or decreased until either the goal is reached or the test ends. To find more details with examples of calculations, see Goal-Based Load Testing.

Configuring a Goal-Based Curve

While configuring a Goal-Based Curve, you are free to use the default or recommended values of the test parameters, or specify custom values according to your goals.

You can start the test with the default Transaction Goal per min but it is recommended to use the actual goal with your website metrics.

To configure the test scenario:

  1. Enter your goal throughput in the Transaction Goal per min box. Automatically adjusted test parameters will be calculated and appear under the respective boxes in the Recommended field.
  2. To set a recommended value for a parameter, click Apply Recommend Values. The values will be applied automatically.

Once the Goal-Based Curve is configured, proceed with Payload and Geo Distribution configuration as described in Getting started with Load Test Setup.

When the test finished, you can view test results on the Load Test Report page. To find if the Transaction goal was reached successfully, check the Transactions per minute chart. Also, it is recommended to check the session log for errors that were detected.