LoadEng - Basic Training
Learn load testing basics, task modeling, and first scenario execution in LoadEng.
Modules
- Load testing fundamentals and core KPIs.
- Scenario and task definition workflow.
- Run execution and live metric reading.
- Using Check and Discovery tools.
Load testing fundamentals
The core objective is to measure how your system behaves under increasing load in a controlled way. Load testing answers not only “does it fail?” but also “at which threshold does performance degrade?”.
- RPS (requests per second): Represents traffic generation rate during the run.
- Latency: Shows how quickly requests are served under load.
- Error rate: Helps detect early quality degradation as traffic increases.
Scenario and task design
In LoadEng, every run is driven by a scenario. A scenario contains multiple tasks, and each task maps to one URL and HTTP method. This allows you to model real traffic behavior across multiple endpoints in one run.
- Identify critical endpoints first (for example: login, search, checkout).
- Assign proper HTTP methods and frequency priorities per endpoint.
- Validate with a small run before scaling.
Running the first test
Treat your first run as a baseline. Start with short duration, low intensity, and a simple parameter set. The first output should guide which single parameter to increase next.
- Start with low concurrency.
- Monitor RPS, latency, and error rate together during execution.
- If anomalies appear, stop safely and review report details.
Interpreting results
Focus on trends, not isolated values. For example, if RPS rises while latency grows gradually and error rate remains low, scaling may be healthy. Sharp latency spikes with rising errors usually indicate bottlenecks.
Basic training checklist
- I can read RPS, latency, and error rate together.
- I can build a realistic scenario/task set.
- I can plan and execute a low-risk first run.
- I can extract clear next actions from reports.