Skip to content
WonderTwin docs

WonderTwin in CI — Integration Guides

WonderTwin in CI

Section titled “WonderTwin in CI”

Run a behavioral twin against your test suite in CI. Get a replay artifact for every run — including failed runs, where you need it most.

Why integrate

Section titled “Why integrate”
  • Beat the bare vendor sandbox. Real rate-limit asymmetry, deterministic seeding, run-scoped state isolation, request-level replay capture.
  • Debug failures in seconds, not hours. A failed CI run produces a downloadable JSONL bundle with every request and response your code made against the twin during that run.
  • Free OSS twin or licensed. Either works in CI. Licensed runs unlock production-grade rate limits and surface in your org’s WonderTwin dashboard.

Pick your CI platform

Section titled “Pick your CI platform”
PlatformGuideStatus
GitHub Actionsgithub-actions.mdstable
CircleCIcircleci.mdstable
GitLab CIgitlab-ci.mdstable
Plain shell / Docker Compose / customshell.mdstable

Don’t see your CI platform? The patterns are the same — see shell.md for the universal recipe and the four ingredients every CI integration needs.

Read this first

Section titled “Read this first”

If you’re new to WonderTwin twins or wt runs, read concepts.md for a 5-minute orientation: what’s a twin, what’s a run, what does the replay artifact contain, what does the license unlock.

How these docs are organized

Section titled “How these docs are organized”

Each platform doc has the same shape:

  1. Snippet — the canonical copy-paste workflow snippet
  2. Setup checklist — secrets, license, twin selection
  3. Variations — deterministic seed, BYO synthetic fixtures, multiple twins
  4. Troubleshooting — gotchas specific to that platform
  5. Reference — links to wt runs CLI docs

The structure is intentional. A future twin-setup-ci skill will programmatically read these guides and adapt them to your repo automatically. See strategy.md for the broader plan.

Contribute a new platform guide

Section titled “Contribute a new platform guide”

The launch set covers ~80% of the SaaS CI landscape, but not all of it. If you run on Buildkite, Jenkins, TeamCity, Argo, Tekton, or something custom and want a first-class guide, follow the template in any existing platform doc and open a PR. The four ingredients (download wt, install license, install + start twin, capture replay) translate directly. We’ll review and merge.