Load Test Lab knowledge library
Make performance testing easier to repeat.
Practical guidance for organizing performance tests, scheduling execution, evaluating results, and keeping the whole team aligned in Load Test Lab.
- 22
- practical guides
- 6
- focused topics
- Load Test Lab
- product workflow
Keep load generation close to the system under test.
Generate load from infrastructure you control while Load Test Lab manages execution requests, results, evaluations, comparisons, and reports.
Read the guideAll resources
Explore the library.
22 guides
Test design and automation
Plan repeatable JMeter tests, define their execution conditions, and automate when they run.
Give every performance test a clear team context.
Manage performance tests, projects, ownership, load parameters, criteria, schedules, evaluations, comparisons, and reports in one workflow.
Keep the conditions of every run attached to the test.
Keep test identity, environment, load parameters, scheduling rules, and JMeter launch method together in one Load Test Lab test.
Turn performance testing into a visible team schedule.
Plan JMeter executions, inspect the monthly calendar, and review the project, test type, and exact scheduled time for each upcoming run.
Turn test execution into a repeatable schedule.
Create fixed, daily, weekly, or monthly performance test plans and review upcoming executions in a shared scheduler.
Add workflow without rewriting trusted scenarios.
Keep JMeter as the execution engine and add project ownership, plans, criteria, evaluations, comparisons, notifications, and reports around existing scripts.
Results and regression analysis
Evaluate test outcomes, apply measurable criteria, and detect changes against trusted baselines.
Start every review with the signals that need attention.
Use the Load Test Lab dashboard to review project and test status, evaluation activity, active work, and recent comparison outcomes.
Turn measured values into an explainable verdict.
Evaluate JMeter results against total and per-step error-rate and response-time limits, including explicit tolerance values.
Show exactly what changed from the trusted result.
Compare evaluated results at run and test-step level and classify error-rate and response-time changes as improvement, no change, or worsening.
Explain what changed between two test results.
Compare evaluated performance test results and classify metric changes as improvement, no change, or worsening.
Give every new result a meaningful reference point.
Mark a trusted evaluation as a reference and use it to detect improvements or regressions in subsequent test results.
Teams, access, and reporting
Organize testing responsibilities, control access, and share useful results with the right people.
Give every performance-testing workflow a clear owner.
Organize team users, projects, roles, and account states so performance tests remain owned and accessible to the right people.
Give each user the access their job requires.
Choose the narrowest Load Test Lab role for administration, technical testing, management, trial use, or report-oriented access.
Turn raw test output into a reviewable outcome.
Evaluate performance test results against explicit criteria and share generated evaluation and comparison reports with selected team members.
Know what runs locally and what the platform stores.
Understand Agent credentials, customer-controlled execution, platform synchronization, role permissions, and temporary file-download links.
Infrastructure and connectivity
Choose where load is generated and connect testing infrastructure to private environments safely.
Keep load generation on infrastructure you operate.
Operate JMeter and the load generator on infrastructure you control while Load Test Lab coordinates execution and stores the resulting workflow history.
Measure the application instead of an unrelated tunnel.
Run JMeter from a customer-controlled host with the required target access so generated test traffic does not need to pass through the Load Test Lab platform.
Keep load generation close to the system under test.
Generate load from infrastructure you control while Load Test Lab manages execution requests, results, evaluations, comparisons, and reports.
Platform and customer stories
Understand the commercial model, the people behind the platform, and how it is used in practice.
Pay for the workflow instead of resold load capacity.
Separate customer-owned JMeter capacity from subscription access to scheduling, evaluation, comparison, notification, and reporting workflows.
Practical workflows based on real product capabilities.
See realistic Load Test Lab workflows for release checks, recurring tests, baseline comparisons, and shared reporting.
Make performance testing a shared, repeatable process.
Load Test Lab helps teams organize performance testing projects, schedules, evaluations, comparisons, notifications, and reports.
Comparison guides
Use a neutral evaluation framework when comparing load-testing workflow platforms.
Compare the execution model before comparing feature lists.
A neutral framework for comparing customer-controlled execution with a managed load-testing platform.
Evaluate the workflow your team will operate every week.
A neutral framework for comparing load-testing workflows, infrastructure ownership, results, reporting, and platform cost.
No guide matches your search.
Put it into practice
Build a clearer performance testing workflow with Load Test Lab.
Start with one real result and build a repeatable workflow around your existing infrastructure.