Test planning
Keep the conditions of every run attached to the test.
A performance result is only useful when its execution context is clear. The Test page stores descriptive data, load parameters, plan settings, criteria, evaluations, comparisons, notifications, and reports under the same test record.
By Load Test Lab product team Reviewed by Kedros, a.s. Updated Product version 1.0.0
Test detail
Test data⌃
Test parameters⌃
Test criteria⌄
Notification configuration⌄
Report configuration⌄
Preview of the current Load Test Lab interface. Example data only.
Describe what is being tested
Test data includes name, description, labels, test type, application, application version, environment, project, timestamps, and the user who last updated the record.
Define the load profile
Test parameters record duration, ramp-up, peak, and load as the number of users. These values remain visible beside the result history so reviewers can confirm the conditions behind a verdict.
- Test duration
- Ramp-up
- Peak
- Load (number of users)
Connect a plan and launch method
A fixed plan contains one or more execution dates. A recurring plan adds a validity range, recurrence type, execution times, and selected weekdays or month days. Both use a launch method, with Agent topologies for JMeter with or without a proxy and master-slave variants.
Put Load Test Lab into practice
Prove the value with a real test.
Start with the scripts and load generator your team already uses.