Stress Testing/Execution

In this chapter, we will explore the execution scenarios, processes, and analytics for stress testing in PruTAN.

Scenario 1: 10 Users Ramp Up in 10 Seconds Using Mode: Volume & Test Plan: Ramp Up

We have configured the following parameters for this test:

  • Users: 10
  • Timeout: 1000ms
  • Warm-Up: 0ms
  • Execution Timeout: 10000ms
  • Delay: 0ms
  • Start Value: 1
  • Increment: 1
  • Max Value: 10
  • Ramp-Up Period: 10000ms

We will add a single script and different time period buckets.

Steps:

  1. Create a collection and a request within the collection.
  2. Select the created request, set the mode to Volume, and choose the Test Plan as Ramp Up.
  3. Provide the necessary data as specified above.
  4. Add scripts using the Add Script button.
  • Scripts are created in the API module.
  1. Add buckets using the Add Bucket button.
  2. Save the configured request and click "Run" to initiate the performance test.
  3. Navigate to Stress >> Analytics >> Collection >> Request.
  4. Select the request to view detailed performance results at the bottom of the page.

Image 1: Stress Execution

The stress execution interface shows the configuration panel where you can set up your performance test parameters. Here, you can see fields for selecting the test mode (Volume), test plan (Ramp Up), and various timing parameters like timeout, warm-up period, and execution timeout. The interface also includes sections for adding scripts (created in the API module) and defining time buckets for result categorization.

Image 2: Analytics

The analytics view displays comprehensive performance results after test completion. Users can observe key metrics such as total transactions, successful transactions, errors, timeouts, transactions per millisecond (Tpms), latency, and response times. The results are organized by time buckets, allowing you to analyze performance trends throughout the test duration. This data helps identify system bottlenecks, measure scalability, and assess overall application resilience under load.

If users want to conduct a performance test using other Test Plans or Modes, they can follow a similar set of steps with adjustments for the specific scenario requirements.