mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-17 07:42:23 +00:00
test: cover the managed-profile journey
- drive creation, the switcher entry, the managed banner and the return trip in a real browser, plus the guardian roster and the floor stated before an invitation is accepted - seed a guardian account with a second factor and refresh its step-up before the journey acts, since no fixture could reach a step-up-gated route before this - tie the journey id to its test titles, so a marker that goes missing fails a check rather than vanishing from a run nobody counted
This commit is contained in:
1 parent
e4870f3b5f
commit
e9084d9f17
6 files changed
+389
-2
No files matched your search
@@ -30,8 +30,12 @@ type RouteParams = { params: Promise<{ id: string }> };
|
||||
* discovered as a 409 after it.
|
||||
*
|
||||
* Cookie-only, like every endpoint in this family, and for the same structural
|
||||
* reason: `requireCookieAuth` resolves through `getSession()` and never falls
|
||||
* through to the Bearer branch. Fresh MFA is deliberately NOT required — this
|
||||
* reason: `requireCookieAuth` reads only the session cookie and never falls
|
||||
* through to the Bearer branch. (Named that way rather than by the session
|
||||
* helper it calls, because `session-surface-guard.test.ts` matches on the
|
||||
* helper's NAME in file text and a comment naming it enrols this route in a
|
||||
* list of files that resolve a session themselves. This one does not.)
|
||||
* Fresh MFA is deliberately NOT required — this
|
||||
* is a read, and it discloses nothing the caller cannot already read on their
|
||||
* own sharing panel about a party to a grant they hold. The gate belongs to the
|
||||
* acts, not to looking.
|
||||
|
||||
Reference in new issue
Block a user