Paid add-on

Performance Targets (SLOs) and Under-Load Traceability

Say what "fast enough" means once, and see it judged on every run and in your requirements matrix.

A checkout performance target, p95 under 800 ms and errors under 1% on staging, met in functional runs but missed in a load test at 180 virtual users; the requirements matrix shows REQ-12 passed functionally but missed under load, REQ-08 passed and met, and REQ-15 passed with no target

What It Does

Performance usually lives outside the requirements process: a load report in one tool, a requirement in another, and nobody able to say which requirement was verified under load. Performance targets close that gap. Keep them under Project settings, attach them to load tests, and link them to requirements. Functional runs give you an early signal without running any load, because the target is checked against a window of recent response times for that endpoint. When a load test judges the target, the matrix records the result in its own Under load column. Each run is compared with the scenario's pinned baseline (or the previous run) using a statistical test over every interval's p95, so a change within normal variation is not reported as a regression.

Overview

A performance target states what good looks like, for example "Checkout p95 under 800 ms and errors under 1%, on staging". Targets are judged two ways: continuously, against the response times of your ordinary functional runs of that endpoint, and inside any load test that attaches them. Link a target to a requirement and the traceability matrix gains an Under load column showing met or missed, right beside the functional verdict and never replacing it. A requirement can pass every functional test and still miss its target under load; now you see both.

Key Capabilities

Targets on p95, error rate and more, per endpoint and environment

Judged continuously on functional runs, with no load test needed

Judged inside load tests, and can stop a run early when missed repeatedly

Under load column in the requirements traceability matrix

Baselines with a statistical comparison, so noise is not called a regression

The Project Assistant can explain a report or propose a target for you to accept

How It Works

1
Add a target under Project settings, for example p95 under 800 ms and errors under 1% on staging
2
Link it to the requirement it protects
3
Functional runs of that endpoint are checked against the target continuously
4
Attach the target to a load test; missing it can stop the run early
5
Read met or missed in the matrix's Under load column, beside the functional verdict

Available on

Performance & Load Testing add-on (paid add-on)

Added to a Professional, Custom or Enterprise licence. Included in the 15-day free trial — no credit card required.

Start Free Trial View Pricing

Performance & Load Testing add-on: a paid add-on to Professional, Custom and Enterprise — included in the Trial

See pricing →