What problem does it solve?
Authgear-server e2e validation requires precise environment resets, YAML structure, and matcher expectations, so this guide consolidates the operational knowledge needed to write deterministic, discoverable tests without missing required steps.
Core Features & Use Cases
- Maintain a fresh test ecosystem by running make teardown and make setup (or the gmake shim) before executing the go test runner, ensuring migrations and binaries match the code under test.
- Organize each scenario as a YAML file under e2e/tests/<feature>/, naming it *.test.yaml, describing steps with actions like create, input, query, audit_query, http_request, admin_api_graphql, and sleep, and adding optional before hooks or authgear.yaml overrides.
- Apply template variables such as {{ .AppID }}, {{ .prev }}, OTP helpers, nodeID encoding, plus Sprig functions, matcher patterns like [[string]]/[[array]]/[[ignore]], and audit-aware SQL tips to assert dynamic results reliably.
- Use this workflow to validate flows such as signup with OTP delivery, fraud protection decisions recorded in the audit log, HTTP token issuance, and admin mutations while keeping commands sequential in the same shell when daemons die on exit.
Quick Start
Request an e2e YAML test case that validates the signup flow for authgear-server.