SDODS — release evidence, not just green checks
Open-source BDD test automation for UI, API and hybrid flows that leaves screenshots, requests and run history behind every run. Multi-project and multi-environment, data-driven, self-healing, with a web UI, an MCP server and AI agents.
Learn SDODS in 7 short lessons
From your first run to agents and CI, about 37 minutes in all. Start at the beginning, or jump to your level.
What SDODS is, the five ideas it is built on, and a first run from install to report.
Beginner
Intermediate
Advanced
Every command and screen in these lessons is real SDODS output. Captions are included; the narration is synthesized.
One command. It checks Node, installs Bun if you need it, fetches SDODS and Chromium, and puts sdods on your PATH.
curl -fsSL https://sdods.com/install.sh | sh
Windows, pinned versions and air-gapped machines: all the install paths.
One language for UI, API and hybrid
Gherkin with a single merged fixture set: seed through the API, assert in the browser.
Projects and environments
A YAML file per project, a YAML file per environment, six-layer precedence you can explain with one command.
Data and user pools
CSV, JSON, YAML, database tables and factories per environment. Users leased per worker with login reuse.
Screenshot narratives
Before and after every UI step for regression suites, start and end for smoke, pixel baselines for visual.
SQLite or Postgres
Run history, flakiness and locator fragility in a database you switch with one command.
MCP and agents
SDODS is an MCP server; agents plan, generate, heal and upgrade tests but only write proposals.
Apache-2.0