Skip to content

Steps

Step Notes
click: <sel> Also dblclick:, rightclick:, or { target, button, count }
fill: <sel> = <value> Replaces the field’s content. = "" clears; a quoted value keeps its spaces; { target, value } too. On macOS the field is checked afterwards and retyped once if keys were lost
type: <text> Types into the focused element; { target, text } focuses the target first
press: <keys> Enter, Escape, Tab, F1…F12, Mod+S (⌘ on macOS, Ctrl elsewhere), Meta+Shift+K
select: <sel> = <option> By label, then value
check: <sel> · uncheck: <sel>
hover: <sel> · focus: <sel>
scroll: down Or a selector (into view), or { target, dx, dy }
drag: { from, to } Options: at: (center, top, bottom, left, right, { x, y }), modifiers: (Alt, Shift, Control, Meta, Mod), hold:. file: instead of from: drops a file. Either end may be in another app
resize: 1280x800 Browser viewport, Electron content area, or desktop window; also { width, height }
open: <url> Web apps
launch · launch: <app> Restart the test’s app, or replace it
close · close: <app> Quit the test’s app, or another one
wait: <condition> exists, absent, visible, enabled, url, equals: [a, b], not:, { app, running }, { app, frontmost }. wait: 500ms exists, but conditions are better
screenshot · screenshot: <name> Also runs the accessibility check
run: <command> See below
ai: <instruction> Reserved for model-driven steps; fails with NOT_IMPLEMENTED until a provider is configured

expect:; see Assertions.

Step Notes
call: <flow> + with: { … } Run a flow with parameters
set: { name: value } Set variables; values may read the app: ${text(sel)}, ${value(sel)}, ${count(sel)}, ${url()}, ${title()}, ${clipboard()}. set: { clipboard: … } fills the clipboard
if: <condition> + then: / else: Checks once; with timeout: waits up to that long for it to become true
repeat: 3 + do: ${index} inside
each: [a, b] + as: item + do: Also a comma-separated string or ${var}
in: <app> + do: The steps work in another app; back in the test’s app afterwards
Option Does
timeout: 10s How long this step waits
optional: true A failure is skipped, not fatal
label: … A readable name in results
- run: npm run db:reset # sh -c (cmd /C on Windows), or defaults.shell
- run:
script: scripts/seed.sh # from the project root
args: [--user, "${email}"] # passed as-is, no shell splitting
env: { API_URL: "${base}" }
cwd: tmp
code: [0, 3] # passing exit codes (default 0); `any` never fails
shell: bash # for cmd: sh, bash, zsh, pwsh, powershell, cmd
windows: { script: scripts/seed.ps1 } # per OS: macos | linux | windows | unix
timeout: 5m # default 2 minutes

A cmd: without shell: uses defaults.shell from sisyphus.yaml, else sh (cmd on Windows). On Windows, sh and bash (and .sh scripts) run in Git Bash from Git for Windows, never the bash on PATH (usually WSL’s, which runs in a Linux VM with other paths); without Git for Windows the step fails with COMMAND_FAILED.

script: picks its interpreter from the extension: .sh, .bash, .zsh, .ps1, .bat/.cmd, .py, .js/.mjs/.cjs, .rb; anything else runs as a program. Afterwards ${output} holds stdout (trimmed) and ${exit_code} the code. A code not in code: fails with COMMAND_FAILED. Not sandboxed.

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