Variables across a test set, file comparison, and JavaScript steps
TL;DR
Prerequisite Test Case in Test Set now pass on what it creates, plus a new File Compare step, sequential execution behavior, and JavaScript steps.
FEATURE
- Prerequisite variables: prerequisite tests hand off runtime variables to every downstream test in the set.
- File Compare step (beta): compare expected vs actual files with AI guidance and variable interpolation, without leaving the runner.
- Sequential execution: run a set or campaign in predictable alphabetical order, stopping at the first failure or continuing through.
- JavaScript steps: write and run JS in a built-in editor, isolated in its own tab, with access to variables and prior results.
- Thunders MCP: expanded toolset to clone a test case, update a step, insert a step, and update an environment.
IMPROVEMENT
- API body editor: the API step JSON body is a full variable editor, with autocomplete, highlighting, and inline references.
- Resolved variable preview: see the real runtime value a step will use instead of raw tokens.
- Ownership: reassign test case ownership individually or in bulk.
- Domain allowlist: skip noisy third-party calls during page-load checks, per project.
FIX
- Variable rename: renaming a variable from project or environment variables now updates every step that uses it.
- Editing conflicts: if a test case changed since you opened it, you now get a clear version-conflict message instead of a generic error.
- Step type preserved: editing a browser step keeps it as a browser step instead of reverting to an AI step.
- Duration overflow: run duration no longer overflows in aggregated runs.
Ready to ship faster with smarter testing?
