raystack / frontier / 33429109833
50%
main: 49%

LAST BUILD BRANCH: feature/featauthenticate-separate-login-from-signup-with-an-explicit
DEFAULT BRANCH: main
Ran
Jobs 1
Files 310
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 50.11%. Remained the same
33429109833

Pull #1916

github

rohanchkrabrty 
test(e2e): cover intent and consent across every auth strategy

The cross-cutting matrix for RFC 0002 (docs/rfcs/0002-explicit-consent-at-signup.md),
through a real server: the three intents against an address that does and does not
have an account, at both enforcement points, one case per strategy, and the complete,
incomplete and unknown-id consent sets. This is the coverage no single ticket in the
stack owns, because it spans the intent, the consent rules and every strategy at once.

Two suites, because app.consent is read at boot and cannot be changed on a running
server. The enabled one drives mail OTP through test users, OIDC through mockoidc,
and passkey up to the ceremony; the disabled one is the promise the RFC makes to
every existing deployment, that nothing changes.

The rollback case injects a failing insert on user_consents with a trigger, because
nothing in the API can produce one: a bad payload is rejected before the transaction
opens, and a well-formed write satisfies every constraint on the table. The suites
read users and user_consents directly for the two things the API deliberately does
not serve, the absence of a user row and the contents of a consent record.

Neither passkey finish method is reachable, for two different reasons, and a skipped
case says so rather than leaving the hole invisible. The register method validates
the attestation before it reaches the gate, so the gate sits behind a ceremony no
test here can perform. The login method runs the gate first, but reaching it needs
an account carrying a passkey_credentials blob, which only that same ceremony writes.
They are untested at unit level too, since the finish flow unit tests drive mail OTP.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Hf1XuPCWcHZ7QY5u4WBB2G
Pull Request #1916: test(e2e): cover intent and consent across every auth strategy

20574 of 41058 relevant lines covered (50.11%)

15.97 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33429109833.1 310
50.11
 GitHub Action Run
Source Files on build 33429109833