Everything you need to ship governed Agentic QA.
Guides, references and playbooks for teams building resilient end-to-end tests with autonomous agents.
Quickstart
Create your first project, connect an environment, and run a governed scenario in under 10 minutes.
ReadNatural Language Scenario Authoring
Write user journeys in plain English. Assertive compiles them into deterministic, replayable steps.
ReadCI/CD Pipeline Triggers
Fail the build on regressions. Wire Assertive into GitHub Actions, GitLab CI, and any HMAC-signed pipeline.
ReadSecret Vault & 2FA Handling
Store TOTP seeds, bypass codes, and API keys. Reference them safely in scenarios with {{secret.KEY}}.
ReadSelf-Healing Selectors
Re-ground DOM targets semantically when the UI drifts. See what healed and why — every run.
ReadAPI Reference
Trigger runs, poll status, and fetch reports via the public REST API.
ReadTesting protected staging sites
If your staging site sits behind Cloudflare Access, Vercel protection or basic auth, add access credentials under Project → Secrets → Protected site access. They are encrypted and sent only to your project's own domain and its subdomains.
- In Cloudflare Zero Trust, go to Access → Service Auth → Service Tokens and click Create Service Token.
- Copy the Client ID and Client Secret (the secret is shown once).
- In your Access application, add a policy with action Service Auth that includes this token.
- In Assertive, choose Cloudflare Access service token, paste both values and click Save.
- Click Test connection. You should see Access OK.
On-prem runner: set ASSERTIVE_CF_ACCESS_CLIENT_ID and ASSERTIVE_CF_ACCESS_CLIENT_SECRET in your local .assertive.env instead; they never leave your host.