Spitfire 0.62.7 release notes
Released: 2026-10-31
- Creating a test from an OpenAPI / Swagger document finds the sign-in: a login operation (a POST like /login or /auth/token, or one whose response carries a token) or an OAuth2 password / client credentials flow is picked, and its body fields (username, password…) come as boxes.
- Try sign-in: the request is sent once from the controller; it shows whether it worked, what the server answered and whether the token is where the test will look (the token itself is never shown).
- Even when it can't be reached, the test is made with a step that signs in once at the start for each virtual user; the token goes into the {{token}} variable and every request after it sends it. The login operation is not a separate step and asks for no write confirmation.
- When nothing is found, give a token, an API key or a Basic username / password yourself; operations that need authentication carry a lock in the list. Docs: Import → Sign-in.
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.