Skip to main content

Get Started with Load Testing

Last updated on

Load Testing simulates user traffic to validate your system's performance under expected and peak load conditions. Identify bottlenecks, validate scalability, and ensure your applications can handle production workloads before they face real users.

Feature Flag

Load Testing is currently behind a feature flag (CHAOS_LOAD_TESTING_ENABLED). Contact your Harness sales representative to get it enabled for your account.

Key Concepts​

Virtual Users​

A virtual user (VU) simulates a real user interacting with your application. Each virtual user independently executes the scenario you define: sending HTTP requests, waiting for responses, and looping through the sequence for the duration of the test.

The Number of Users setting controls how many virtual users run concurrently at peak load. Higher concurrency means more simultaneous requests hitting your system.

Load Profile​

The load profile describes how virtual users are added over the course of a test. Harness Load Testing uses a ramp-up then steady-state model:

Users
  |         ___________________
  |        /
  |       /
  |______/
  |________________________________ Time
     ^          ^
  Ramp-Up    Steady State

Ramp-Up Phase — Virtual users are added linearly from 0 to the target number over the Ramp-Up Duration. This gradual increase avoids overwhelming the system at the start and lets you observe how it responds as load increases.

Steady-State Phase — After ramp-up completes, the configured number of virtual users continues running for the remainder of the Test Duration. Steady-state duration = Test Duration - Ramp-Up Duration.

Example: 600s total duration with 120s ramp-up gives 480s at peak load.

Load Test Frameworks​

Locust is a Python-based, open-source load testing framework and the currently supported framework in Harness Load Testing. Locust models user behavior as Python classes, making it straightforward to script complex scenarios like authentication flows, session-based interactions, and conditional logic. JMeter and K6 are coming soon.

Scenario Definition​

A scenario defines the sequence of HTTP requests your virtual users execute. Each request includes:

  • HTTP Method: GET, POST, PUT, DELETE, PATCH, etc.
  • Endpoint URL: The full URL for UI-defined tests, or a path relative to the Host URL for script-based tests
  • Request Name: An optional label for identifying the request in results
  • Query Parameters: URL query string parameters as key-value pairs
  • Headers: HTTP request headers (e.g., Authorization, Content-Type)
  • Assertions: Conditions that must be true for the request to count as a success
  • Extractions: Values captured from responses and reused in later requests

Assertions​

Assertions define success criteria for each request. A failed assertion marks that request as an error in the test results.

Assertion TypeWhat it checks
TextThe response body contains (or does not contain) a specific string
Response TimeThe request completes within a specified time threshold (milliseconds)

Extract from Response​

Response extraction captures a dynamic value from a response (such as a token returned after a login request) and makes it available as a variable in subsequent requests. This enables realistic multi-step flows like:

  1. POST /auth/login — extract access_token from response body
  2. GET /api/user/profile with Authorization: Bearer {{access_token}}

Host URL​

When uploading a Python script, the Host URL is the base URL of the application under test. Locust prepends this to all relative paths in your script. For example, with Host URL https://api.example.com, a request to /users becomes https://api.example.com/users.

Load Test Infrastructure​

Load tests run on infrastructure managed by the Harness chaos agent. Two target types are supported:

Target TypeHow it worksBest for
Linux VMThe agent on a Linux host runs the Locust process locally and streams results back to Harness.Simple setups, on-premises hosts, direct network access to internal services.
KubernetesThe agent orchestrates a master pod and optional worker pods inside a Kubernetes cluster. Requires v1.85.3+. Load testing is enabled by default — no additional configuration needed.Scalable distributed testing, cloud-native environments, high-concurrency workloads.

When creating a load test, you select a target type first, and the Load Test Infrastructure dropdown filters to show only infrastructure matching that type. See Infrastructure Types for setup instructions.

Test Definition Modes​

The available test definition modes depend on the target type you selected:

ModeLinux VMKubernetesDescription
Define test via UI✅✅Build HTTP scenarios visually without writing code. Harness generates the Locust script at execution time.
Upload Python Script✅✅Upload a custom .py Locust script for full control over user behavior.
Using Image—✅Use a prebuilt container image as the load test source. Kubernetes-only since the image runs as a pod in the cluster.

Prerequisites​

  • Access to the Harness Resilience Testing module
  • A chaos infrastructure configured in your project (Linux VM or Kubernetes)
  • An environment created in your project for the infrastructure
  • Target application endpoints accessible from the test infrastructure

Quick Start​

  1. Navigate to Resilience Testing > Load Testing
  2. Click + New Load Test and follow the guided creation flow
Try Sample Test

Click the + New Load Test dropdown and select Try Sample Test to instantly explore the feature with a pre-configured test: sample endpoints, realistic load settings, and example configurations included.

For the complete step-by-step walkthrough, choose your infrastructure type:

Next Steps​