This page lives under /docs/qa/ and is the authoritative reference for how we test and validate the sign-in flow. It exposes test-runner internals (testIDs, fixture names, runner-step captions) by design — the audience is engineers writing flows, reviewing test failures, or reasoning about coverage. Customer-facing sign-in documentation is generated separately from this same spec; do not link readers here from public marketing or onboarding content.
This page lives under /docs/qa/ and is the authoritative reference for how we test and validate the sign-in flow. It exposes test-runner internals (testIDs, fixture names, runner-step captions) by design — the audience is engineers writing flows, reviewing test failures, or reasoning about coverage. Customer-facing sign-in documentation is generated separately from this same spec; do not link readers here from public marketing or onboarding content.
This page lives under /docs/qa/ and is the authoritative reference for how we test and validate the sign-in flow. It exposes test-runner internals (testIDs, fixture names, runner-step captions) by design — the audience is engineers writing flows, reviewing test failures, or reasoning about coverage. Customer-facing sign-in documentation is generated separately from this same spec; do not link readers here from public marketing or onboarding content.
This page lives under /docs/qa/ and is the authoritative reference for how we test and validate the sign-in flow. It exposes test-runner internals (testIDs, fixture names, runner-step captions) by design — the audience is engineers writing flows, reviewing test failures, or reasoning about coverage. Customer-facing sign-in documentation is generated separately from this same spec; do not link readers here from public marketing or onboarding content.