Performance testing
Turn any request or flow into a load test, choose the concurrency and duration, and read latency percentiles, throughput, and error rate. Set thresholds so a regression fails the build, and watch the trend over time.
The request you already send and the flow you already run are the load test. Point a performance run at them, and you are testing the exact calls your app makes, with the same auth, variables, and bodies.
There is nothing new to script and nothing to keep in sync with your functional tests.
Dial in how many requests run in parallel and for how long, and ramp up to find where things bend. Model a realistic peak or push until something breaks, on purpose.
Averages hide the pain. Performance runs report p50, p95, and p99 latency alongside throughput and error rate, so you see what your slowest users actually experience, not just the mean.
Charts make the tail and the error spikes obvious at a glance.
Set a ceiling: p95 under 300ms, error rate under 1 percent. A run that breaches it fails, so a performance regression stops a release the same way a broken assertion does.
Thresholds run in CI, so slow code is caught in review, not by your users.
Runs are stored in the cloud, so you can see whether last week's change made the p95 worse and when a slowdown crept in. Performance becomes a line you watch, not a one-off you forget.
Choose the calls to load test. They run with the same auth, variables, and bodies as your functional tests.
Choose concurrency and duration, and set thresholds for p95 latency and error rate.
Run from the CLI in a pipeline so a breach fails the build, or run ad hoc while you tune.
Read the percentiles and error rate, and compare against previous runs stored in the cloud.
No. A performance run reuses an existing request or flow, with the same auth, variables, and bodies, so there is nothing new to script or keep in sync.
p50, p95, and p99 latency, throughput, and error rate, shown as charts so the tail and any error spikes are easy to spot.
Yes. Set thresholds such as p95 under 300ms or error rate under 1 percent, and a run that breaches them fails in CI like any other gate.
Runs are stored in the cloud, so you can track p95 and error rate across releases and see exactly when a regression crept in.
The desktop app is free and open source. Add the cloud when you want hosted mocks, monitoring, and a shared broker.