Test run options

NeoLoad Web offers multiple ways to run a performance test, such as starting a test manually from the UI or automating it through your CI/CD pipeline. The right option depends on how much control you need over when and where your tests run.

This topic explains each option and helps you decide which one fits your workflow.

Run options

NeoLoad Web offers the following ways to run tests:

Option

Description

Resource allocation

Resource requirements

Manual run

Configure the test in the UI and trigger the run manually.

NeoLoad Web allocates resources automatically.

Available controllers and load generators.

Reserved run

Lock a controller, load generators, and virtual users for a specific time slot. Essential when teams share infrastructure and need guaranteed availability.

Pre-allocated through a reservation.

An active reservation with the right resources.

Scheduled run

Combine a reservation with an automatic test start. The test launches on its own when the time slot begins.

Pre-allocated through a reservation.

An active reservation with the right resources.

CI/CD-triggered run

Trigger tests from your pipeline through the NeoLoad Web API and an access token. Define quality gates to pass or fail builds automatically.

Automatic or reserved, API-driven.

An access token and API integration.

Test run lifecycle

When you start a test, NeoLoad Web allocates resources, deploys the test to the controller, and prepares load generators. Once everything is ready, virtual users start generating load.

You can monitor real-time metrics in the results view while the test runs. When the test finishes, NeoLoad Web stops virtual users, collects the last data, and displays the results. If you're using a reservation, the system starts winding down 15 minutes before the slot ends.

What's next

Your next steps depend on your goal: