test(e2e): quarantine OIDC token-flow spec blocked on bunyip BUNYIP-146 #319

Merged

nrupard merged 2 commits from fix/PMS-435-quarantine-oidc-token-flow-bunyip-146 into main

2026-06-20 18:47:40 +02:00

David commented

2026-06-20 17:41:28 +02:00

Owner

The OIDC token-flow test (e2e/tests/oidc.spec.ts) fails at the state assertion ("state mismatch", received null) because bunyip's /oauth2/authorize 302s to /login instead of the registered redirect_uri. The PMS-434 diagnostic run (#2098) ruled out an e2e cookie-forwarding defect: setup logged KEEP .a8n.systems#bunyip_op_session and persisted all three OP cookies (access_token, refresh_token, bunyip_op_session) to op-state.json, and the oidcTest fixture loads that storageState into the request context. The session cookie is present, on the correct domain, and replayed - yet authorize still bounces. That is bunyip's COOKIE_DOMAIN / bunyip_op_session scoping issue tracked in BUNYIP-146, not a mokosh-server regression; every other api test and staging health pass.

Quarantine the spec with test.fixme (the same convention auth.spec.ts uses for PMS-148) so this external blocker stops gating unrelated PRs, and document the quarantine in e2e/README.md. Un-fixme when BUNYIP-146 ships.

#PMS-435

The OIDC token-flow test (e2e/tests/oidc.spec.ts) fails at the `state` assertion ("state mismatch", received null) because bunyip's /oauth2/authorize 302s to /login instead of the registered redirect_uri. The PMS-434 diagnostic run (#2098) ruled out an e2e cookie-forwarding defect: setup logged `KEEP .a8n.systems#bunyip_op_session` and persisted all three OP cookies (access_token, refresh_token, bunyip_op_session) to op-state.json, and the oidcTest fixture loads that storageState into the request context. The session cookie is present, on the correct domain, and replayed - yet authorize still bounces. That is bunyip's COOKIE_DOMAIN / bunyip_op_session scoping issue tracked in BUNYIP-146, not a mokosh-server regression; every other api test and staging health pass. Quarantine the spec with `test.fixme` (the same convention auth.spec.ts uses for PMS-148) so this external blocker stops gating unrelated PRs, and document the quarantine in e2e/README.md. Un-fixme when BUNYIP-146 ships. #PMS-435

David added 1 commit

2026-06-20 17:41:28 +02:00

test(e2e): quarantine OIDC token-flow spec blocked on bunyip BUNYIP-146

Create release / Create release from merged PR (pull_request) Has been skipped

Details

E2E / Playwright against staging (pull_request) Successful in 42s

Details

Check / fmt + clippy + compile + unit/doc tests (pull_request) Successful in 1m16s

Details

Integration / integration tests (pull_request) Failing after 5m5s

Details

1a2b2dd9f7

The OIDC token-flow test (e2e/tests/oidc.spec.ts) fails at the `state` assertion ("state mismatch", received null) because bunyip's /oauth2/authorize 302s to /login instead of the registered redirect_uri. The PMS-434 diagnostic run (#2098) ruled out an e2e cookie-forwarding defect: setup logged `KEEP .a8n.systems#bunyip_op_session` and persisted all three OP cookies (access_token, refresh_token, bunyip_op_session) to op-state.json, and the oidcTest fixture loads that storageState into the request context. The session cookie is present, on the correct domain, and replayed - yet authorize still bounces. That is bunyip's COOKIE_DOMAIN / bunyip_op_session scoping issue tracked in BUNYIP-146, not a mokosh-server regression; every other api test and staging health pass.

Quarantine the spec with `test.fixme` (the same convention auth.spec.ts uses for PMS-148) so this external blocker stops gating unrelated PRs, and document the quarantine in e2e/README.md. Un-fixme when BUNYIP-146 ships.

#PMS-435

nrupard added 1 commit

2026-06-20 18:42:31 +02:00