Skip to content

Editing tests

Pick a test in the Tests list to open it. The list has a filter (by name or tag) and quick filters: All, Failed, Flaky, Not run. A data-driven test shows how many rows it has. The Flows tab lists your flows.

Each test opens in one of two modes, and you can switch at any time:

  • Steps: one row per step, in plain words (Fill in textbox "Email" with ada@example.com). Nested steps (each, if, in, flows) are indented groups.
  • Source: the YAML itself, with completion for steps, options, flows, variables and the real elements Studio has seen in your app, and hover help for every key.

Edits in either are saved automatically, and only the steps you changed are rewritten: your comments and formatting stay as they were.

  • Add step at the end of a list, or below any step, and pick its type.
  • Change a step’s type, duplicate it, delete it, or drag it by its grip to move it.
  • Add options (a timeout, optional, a check’s text or count) from the row.
  • Use a flow with Use flow; its parameters appear as fields.
  • Extract into a flow turns selected steps into a new flow and replaces them with a call.

Studio runs the same checks as sis validate as you edit. Problems are listed above the editor with their line: unknown roles, bad patterns, flows that don’t exist. Hints come with one-click fixes, for example replacing steps that repeat a flow with a call:.

Run runs the open test. Its menu holds the options: Show the app to watch it, pause at the first step, and more. Debug runs it in the debugger. Results appear in the side panel as steps run, and each step row gets a ✓ or ✗.

Suites from sisyphus.yaml run from the play button above the Tests list.

If a test changes on disk (your editor, git pull, an AI agent), Studio reloads it. If you also have unsaved edits, it asks which to keep rather than overwriting either.

Made by Bussin Bytes© 2026 Bussin Bytes Ltd · sisyphus.bussinbytes.io