Glossary
New to NeoLoad Web? This glossary explains our most commonly use terms.
|
Term |
Description |
|---|---|
|
Access token |
An access token lets external tools interact with NeoLoad Web without a password. |
|
Agent Performance Testing (APT) |
Agent Performance Testing (APT) is an AI agent that analyzes a test result when you request it and produces an AI report. |
|
Augmented analysis |
Augmented analysis uses machine learning to segment a test result into time intervals and assign key insights to each one. |
|
Baseline |
Baseline is a reference test result used to compare against future test runs to identify performance trends and regressions. |
|
Concurrent runs |
Concurrent runs are how many tests can run at the same time with your current license capacity. |
|
Controller |
The Controller decides how many virtual users to generate, directs load generators, and tracks test results. |
|
Dashboard |
A dashboard is a customizable interface that allows testers to visualize and focus on specific performance metrics from test results. |
|
Dedicated IPs |
Dedicated IPs are fixed IP addresses reserved for your tests, so you can set your firewalls to allow traffic from the fixed IPs. |
|
Deletion policy |
A deletion policy automatically removes outdated test results from a workspace. |
|
Dynamic infrastructure |
Dynamic infrastructure automatically provisions controllers and load generators in a Kubernetes or OpenShift cluster. |
|
Event |
An event is a key action or issue during a test, such as an alert, error, or objective. |
|
Guaranteed VUs |
Guaranteed VUs are virtual users reserved for a single workspace so it always has capacity. |
|
Interval |
An interval is a time range you define to filter and analyze a specific part of a test result. |
|
JMeter test |
A JMeter test runs from NeoLoad Web using a Controller, with its results available in NeoLoad Web. |
|
LDAP |
LDAP connects a directory of users and groups, so they can be retrieved and authorized in NeoLoad. |
|
Load generator |
A load generator creates the virtual users that simulate real application usage. |
|
Load infrastructure |
The combination of controllers and load generators used to execute a performance test scenario. |
|
Load policy |
A set of rules that define how virtual users simulate load on the system under test during a test scenario. |
|
Model Context Protocol (MCP) |
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to NeoLoad Web to run tests and analyze results. |
|
Objectives |
An objective is a performance target or success criteria defined within a test to evaluate whether an application meets expected performance levels. |
|
Offline lease |
An offline lease transfers license capacity from NeoLoad Web to either NeoLoad GUI or another Neoload Web instance. |
|
Passed and Failed status |
The final status of a test run indicating whether it met predefined performance objectives (passed) or fell below expectations (failed). |
|
Performance test types |
Performance test types are common test patterns such as load, spike, stress, soak, and failover. |
|
Population |
A population is a group of simulated users interacting with your application in a scenario. |
|
Project |
A project is a NeoLoad configuration that defines the test setup, including scripts, scenarios, and load policies, for a specific application under test. |
|
Regression detection |
Regression detection compares current results against objectives to identify performance regressions. |
|
Reservation mode |
Reservation mode locks a controller, load generators, and virtual users for a time slot. |
|
Scenario |
A scenario is a structured set of conditions and configurations that define how a test is run, including virtual user behavior, load policies, and test objectives. |
|
Scheduled run |
A scheduled run is a reservation that also starts the test automatically when its time slot begins. |
|
Service Level Agreement (SLA) |
A Service Level Agreement (SLA) defines the performance criteria a test result is measured against. |
|
Single Sign-On (SSO) |
Single Sign-On (SSO) provides SAML 2.0 sign-in through an identity provider, without separate NeoLoad Web credentials. |
|
Subscription |
Your subscription defines your account plan, expiration, and real-time usage of credits and resources. |
|
System Under Test (SUT) |
The application or software component being evaluated during a performance test. |
|
Test |
A test is a structured unit in NeoLoad with the following items:
|
|
Test result |
A test result is data collected from a single execution of a test, which can be analyzed in isolation or within the context of a test to track performance trends. |
|
User roles and permissions |
User roles and permissions are role-based access levels that control what each user can do. |
|
Virtual User Hour (VUH) |
A Virtual User Hour (VUH) is a unit equal to one virtual user running for one hour. It lets a test use more virtual users than your license includes. |
|
Virtual Users (VU) |
Simulated users that replicate real user behavior to generate load on the system under test during a test execution. |
|
Webhook |
A webhook sends an automated notification to an external server using an HTTP request when a NeoLoad Web event occurs. |
|
Workspace |
A workspace is a collaborative environment where testers organize tests, test results, and manage user access. |
|
Zone |
A zone defines where a test runs. |