Sisyphus documentation
How to install Sisyphus, write tests for your web, desktop and hybrid apps, run them on your machine or in CI, and read what went wrong.
New here
Section titled “New here”Install SisyphusStudio and the sis command, and the permissions they need.
Your first testWrite a test, run it and read a failure. Fifteen minutes.
How Sisyphus worksProjects, apps, tests, selectors, waiting and results, in plain words.
Test a desktop appThe same kind of test against a macOS, Electron or Tauri app.
Guides
Section titled “Guides”Write testsFinding elements, doing things, checking results, flows, variables, test data and several apps at once.
Run testsRunning suites, reading failures, flaky tests, organising a suite and CI.
Sisyphus StudioEditing, the inspector, the recorder, the debugger and runs.
MoreAI agents over MCP, load testing, accessibility checks and troubleshooting.
Reference
Section titled “Reference”| Page | What’s in it |
|---|---|
| Test files | Every key of a .sis.yaml test or flow |
| Steps | Every step and its options |
| Assertions | Every expect form and property |
| Selectors | The full selector syntax |
| Variables | Every variable and function in ${…} |
| sisyphus.yaml | The project file |
| Command line | Every sis command and option |
| Error codes | What each code means and what to do |
| Platform support | Which apps run on which systems |
Need a hand?
Section titled “Need a hand?”Troubleshooting covers the common problems: permissions, apps that won’t start, elements that can’t be found. New to end-to-end testing? Start with Why end-to-end testing.
Made by
© 2026 Bussin Bytes Ltd · sisyphus.bussinbytes.io
