UI, API and mixed scenarios in one language
Gherkin with one merged fixture set, so a scenario can seed through the API and assert in the browser.
Open source · Apache-2.0 · API tokens are free
SDODS — an automation platform with a reusable architecture
BDD for UI, API and hybrid flows. Multi-project, multi-environment, data-driven and self-healing, with before/after screenshot narratives, a database-backed history, an MCP server, AI agents, GitHub and Jira integration and a web UI.
Install in one line, on any operating system:
curl -fsSL https://sdods.com/install.sh | shWhy SDODS
Software ships when someone is confident enough to say yes. That confidence is usually scattered across a green pipeline, a manual check and a screenshot in a ticket. SDODS turns it into evidence anyone can point at: every scenario tied to a business capability, every run reproducible from one command, every regression explained by the screenshots and requests that produced it.
Many apps, many environments
One YAML per project plus one per environment; strict, explainable configuration precedence; secrets only through ${VAR}.
Reusable data
CSV, JSON, YAML, database tables and faker factories per environment, plus user pools leased per worker with login-state reuse.
Confidence across browsers
Chromium, Firefox, WebKit and mobile emulation; --project-matrix runs every browser you declared, @skip:<browser> is validated by lint.
Readable results
Before/after screenshots per step by suite tag, API request/response snapshots, and a run viewer with slider, overlay and pixel diff.
Institutional memory
Cucumber NDJSON ingested into SQLite or Postgres: flakiness, locator fragility, environment stability and suite health over time.
How it works
Everything is CLI-first. The web UI, the MCP server and the scheduler spawn the same commands and stream their output, so CI needs nothing but Node and the repository.
- sdods CLI
- Config + registry
- Browser runs
- NDJSON + screenshots
- SQLite / Postgres
- Web UI · MCP · agents
See every step
Regression scenarios capture a screenshot before and after every UI step. The run viewer pairs them with a slider, an overlay and a pixel diff. These are real captures from the demo project.
What ships in the box
BDD for UI, API and hybrid
Reusable step library, page objects with decorators, module and process taxonomy.
Data and user pools
Per-environment datasets, factories, leased accounts, cached storage state.
Self-healing locators
Scored candidate probes, persisted heal history, proposals to fix page objects.
Before/after narratives
Screenshot policy by suite tag; visual baselines; API snapshots.
SQLite or Postgres
One schema, runtime toggle, verified switch in both directions.
MCP server and agents
37 tools for Claude Code, Codex, Cursor and VS Code; planner, generator, healer, upgrader.
GitHub and Jira
Check runs, PR comments, deduplicated issues, @jira:KEY links, transitions.
Schedules
Cron recipes with overlap policy; runs from the server, crontab, launchd, systemd or Actions.
Web UI with roles
Organizations, workspaces, projects, modules; run viewer, Gherkin editor, tokens.
Quickstart
curl -fsSL https://sdods.com/install.sh | sh # or on Windows: irm .../install.ps1 | iex
cd ~/.sdods/app
sdods run -p demo-shop -e staging -l api
sdods run -p demo-shop -e staging -l ui -b chromium -t @smokeOnly Node 22 is required. Options, upgrade and uninstall are on the install page and in the installation guide.
Works with Claude Code and Codex
SDODS is an MCP server: sdods mcp install claude or sdods mcp install codex, then ask your assistant to run, analyze or heal tests. Agents can reuse your logged-in CLI session, so no API key is required.
Want a feature? Tell us.
Feature requests and feedback go straight to the maintainers by email. No account with us, no tracking.
Send feedback