Glossary

New to NeoLoad Web? This glossary explains our most commonly use terms.

Baseline	Baseline is a reference test result used to compare against future test runs to identify performance trends and regressions.
Dashboard	A customizable interface that allows testers to visualize and focus on specific performance metrics from test results.
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.
Objectives	An objective is a performance target or success criteria defined within a test to evaluate whether an application meets expected performance levels.
Passed and Failed status	The final status of a test run indicating whether it met predefined performance objectives (passed) or fell below expectations (failed).
Project	A NeoLoad configuration that defines the test setup, including scripts, scenarios, and load policies, for a specific application under test.
Scenario	A structured set of conditions and configurations that define how a test is run, including virtual user behavior, load policies, and test objectives.
System Under Test (SUT)	The application or software component being evaluated during a performance test.
Test	A structured unit in NeoLoad with the following items: Executable unit: Represents a NeoLoad project linked to a scenario and run using load infrastructure. Result container: Stores and organizes results from multiple test runs of the same scenario for comparison and analysis.
Test result	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.
Virtual Users (VU)	Simulated users that replicate real user behavior to generate load on the system under test during a test execution.
Workspace	A collaborative environment where testers organize tests, test results, and manage user access.