Spitfire 0.5.14 release notes
Released: 2026-10-01
- Open k6 and JMeter tests: Tests → Open file turns a k6 script (.js, .ts) or a JMeter plan (.jmx) into a Spitfire test and opens it in the editor. Load model, requests, headers and bodies, checks and assertions, values taken from responses, think times, thresholds and variables are converted; the file is read, never run. What has no equivalent (loops, conditions, custom metrics, data files, non-HTTP requests) is reported with its line number.
- Find the breaking point: from the Run dialog, one scenario's load climbs in steps; each step is judged on its own p95 and error rate, and the first that fails stops the run. The run page states the capacity ("met the criteria at 200 iterations/s, not at 230"), the step table and why; when virtual users ran out, it says that this is not the system's limit.
- Findings: a finished run's page lists what its own numbers show: a clearly slowest step, kinds of errors (5xx, 429, other 4xx, timeouts, refused connections, DNS/TLS), throughput that stopped following the load, iterations that could not start, long connection setup, a gap between locations, failed checks, a regression against the baseline, a long latency tail. A rule fires only when the effect is clear and never claims a cause inside the system.
- Environments: on the editor's Environments tab each environment (staging, production…) gives variables their values and maps the steps' connections to others of the same type. The Run and Schedule dialogs pick the environment, scale the load by a percentage and change variables for that run only; the run records and shows what it used. CLI: --env, --scale, --var.
Updating
Your installation tells you about a new release itself: admins see its notes and the update command for that installation at the top of the UI. The command backs up the database first and keeps the settings (Updating). You can also follow new releases with the RSS feed.