Spitfire 1.2.0 release notes
Released: 2026-11-05latest
- k6 engine: k6 scripts and k6 archives run as they are on runner-k6; results land in the Spitfire report, the script's thresholds are proposed as the test's own and k6's verdict shows as the "k6 thresholds" check. A converted import can be run natively with k6/JMeter.
- JMeter import: requests inside logic controllers are kept in order (what each controller decided is reported), CSV Data Sets become data bindings; CSV files picked with the .jmx are uploaded and bound.
- Postman import: test scripts become extractors and checks; the import page reports each script, where it was and how much was converted.
- Create a test from APM: a service's real endpoint mix, the observed peak and p95 thresholds make 1.5x / 2x / breaking-point tests in one click. A Recommended tests panel and a Regressions card (against last week or the previous version); regressions go to channels as the apm.regression event.
- Write findings back: test findings can be written as events to Zabbix (trapper, acknowledge), Dynatrace (Events v2) and Instana. Off by default; turned on in the connection settings.
- Runner loss: when a runner drops mid-run, the report, the findings and the HTML runner list say so; the run stops or continues on the remaining runners as set.
- High availability and disaster recovery docs: the current state, what happens when the controller is down, scheduled encrypted backups, a restore drill, update and rollback downtime.
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.