1. Docs
  2. Build tests
  3. Report
  4. Load test results

Load test results

When a run contains JMeter or k6 steps, Report shows load-test results instead of the usual browser evidence: a verdict per load step, the numbers that matter, and a comparison with the step’s previous run.

3 min read Updated CustomersAdmins

In short

On this page you can

  • See every load step of a run with requests, errors, P90, throughput and peak users.
  • Read why a step Failed or Passed with warnings.
  • Compare a step with its previous run, request by request.
  • Inspect single requests and responses, and draw extra charts with AI.
  • Download the raw results as JTL, or upload a JTL to a JMeter pipeline run.

How to use it

  1. Open the run; its Summary shows the load verdict and the Load steps table.
  2. Click a step row to open its test case tab with the full report.
  3. Read the verdict strip and Assessment first, then the charts.
  4. Check Compared with a previous run before you call a change a regression.
  5. Pick the view you want in the PDF, then click Export PDF.

Where load tests show up#

RunSummary tabTest case tab
A pipeline whose test cases are all JMeter or k6 stepsLoad verdict, Load steps table, Load Test SettingsThe step’s full load report
A pipeline mixing browser and load test casesThe usual run summaryBrowser test cases: steps. Load test cases: the load report
A JMeter pipeline (results from a JTL file)AI Report Feedback, Load Test Settings, the JMeter report—

The load-run Summary#

The result card shows the run’s verdict, the worst of its steps, with “{passed} of {total} load steps passed”, plus start, duration and who started it.

ColumnMeaning
StepThe JMeter or k6 step and its test case.
ResultThe step verdict.
RequestsRequests sent during the step.
Errors“Requests that failed (no answer, 4xx/5xx, failed assertion). Slow answers are SLA misses, not errors.”
P90“9 of 10 requests were answered within this time.” Amber when requests missed their target.
ThroughputRequests answered per second over the whole step.
Peak usersMost virtual users active at the same time.
DurationHow long the step ran.
vs previous runP90 and error rate against the step’s previous run, or first run.

Click a row to open its test case tab. Load Test Settings lists what the run used: users, duration, load model, think time, targets and whether data came from a data source.

A load step’s report#

In the test case tab, each JMeter or k6 step has its own report. Two views: Summary & charts and Requests / Responses; the first has a Report or Dashboard layout.

  • Verdict strip: Passed, Passed with warnings or Failed with its reasons, for example “12 requests failed (0.4%)” or “saturated at ~80 users”. Few users or requests add “read it as a functional check, not a load test”.
  • Assessment: PASSED or FAILED, Where the time goes per service (share of response time), Most common error and the Response codes.
  • Compared with a previous run: this run against the baseline for Avg response, P90, P99, Throughput, Error rate, Apdex, Requests and Peak users, marked Better, Worse or Similar, also per request. If the load differs it warns “compare with care”. See the rule.
  • Charts: response times, throughput, users and errors over time, distributions and SLA targets.
  • Chart with AI: describe a chart (“p95 response time per service over time”) and click Draw. AI only picks the chart type; every value is computed from the real result rows. Very large result files use the first 500,000 rows.
  • Requests / Responses: the stored sample of requests with label, status, times, headers, bodies and assertions, searchable. “Showing {stored} of {total} requests” tells you it is a sample.

While the load test runs#

A live panel on top of the tab refreshes about every 5 seconds with the running numbers, until the final report arrives. Stopping the run stops a JMeter step within seconds and keeps its partial results.

JTL files#

  • Download JTL saves the step’s raw results (k6 samples come as a JTL-format CSV).
  • On a JMeter pipeline run, Upload JTL takes a .jtl, .xml or .csv file and builds the report from it. Without one: “No JTL report uploaded for this run.”

Load tests in the PDF and email#

The JMeter section of the report PDF follows the view you have open: overall or per sampler, and the services you show. Choose it before you click Export PDF or Share Report. A JMeter pipeline’s own report also has an Export PDF button (“Export charts and tables as PDF”) that builds a PDF of the charts in your browser.

For a written review of the load results, use AI Report Feedback: it adds a Performance review (JMeter) section.

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai
© 2026 Selenity Technology · SmartestQAsmartestqa.aiThis page as MarkdownChecked against smarttest-fe predev 2a8c79cc (automationReportSummaryPage/LoadRunSummary.jsx, LoadTestSettingsCard.jsx, JmeterReportPage/*, stepVerdict.js), smarttest-be 633c2a03