Customer-controlled execution
Keep load generation close to the system under test.
Load Test Lab does not provision a managed load cloud. The Agent runs next to your JMeter installation and uses the network access already available to your load generator.
By Load Test Lab product team Reviewed by Kedros, a.s. Updated Product version 1.0.0
Agent
Configure the Load Test Lab Agent for the active team.
Team Agent
Customer-controlled load generator connection
Team Agent⌃
Preview of the current Load Test Lab interface. Example data only.
Configure the local execution environment
Create and download a team Agent, then configure its JMeter home directory and working directory. Each Agent receives a team-specific topic and credential used for platform communication.
Generate test traffic locally
The application sends execution requests to the Agent. JMeter runs on the customer-controlled host, so generated traffic is not routed through a Load Test Lab load generator.
- Your JMeter installation
- Your load-generator capacity
- Your network route to the target
- Your proxy or master-slave setup
Synchronize results with the platform
Execution status, result files, and log files are synchronized to Load Test Lab for storage, evaluation, reporting, and shared history. Local execution does not mean that all test data remains only inside the customer network.
FAQ
Common questions
Does Load Test Lab provide load-generator capacity?
No. The customer provides and operates the JMeter load generator.
Do result files stay only on the load generator?
No. Result and log files are synchronized with Load Test Lab so the platform can evaluate, report, and retain the run history.
Put Load Test Lab into practice
Prove the value with a real test.
Start with the scripts and load generator your team already uses.