mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 4.7
d3e5ebe441
Introduces roles/test-e2e-playwright/files/personas/ — runGuestFlow,
runBiberFlow, runAdminFlow plus 10 utils (csp, dashboard, env, keycloak,
landing, logout, matomo, prometheus, interaction, index) — and wires
both the Ansible runner (run_one.yml) and the local rerun helper
(scripts/tests/e2e/rerun-spec.sh) to stage the tree alongside
service-gating.js so specs can `require("./personas")`.
First batch of role specs migrated to consume the shared library
(dashboard, keycloak, mailu, matomo, prometheus, web-svc-cdn,
web-svc-simpleicons) — each gets the spec.js persona scenarios plus
the matching meta/services.yml + playwright.env.j2 entries; matomo is
marked role-closed in req 019. dashboard/keycloak/mailu TODO.md
updated; docs/requirements/019 reflects matomo closure.
Reason: req 019 Rule 3 mandates that every role's guest/biber/
administrator flow runs the same canonical steps; centralising them
in one shared library keeps per-role drift from re-introducing the
stub-shaped bodies the new lint forbids.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
57 lines
2.5 KiB
JavaScript
57 lines
2.5 KiB
JavaScript
/**
|
|
* Post-auth app-interaction helpers.
|
|
*
|
|
* Every persona scenario MUST drive a real, role-specific interaction
|
|
* AFTER the auth chain settles — proving the role is not just reachable
|
|
* and authenticated but actually responsive to user input. There is
|
|
* NO generic fallback: a generic "click any visible link" assertion
|
|
* tests nothing role-specific, so this module deliberately refuses to
|
|
* provide one. Each role's spec MUST supply its own `biberInteraction`
|
|
* / `adminInteraction` callback that exercises a meaningful surface
|
|
* (post a message, open a settings tab, browse a content list, ...).
|
|
*
|
|
* `runRoleInteraction` is a thin trampoline: when the spec passes a
|
|
* callback through `runBiberFlow` / `runAdminFlow` opts, the callback
|
|
* runs; when it does not, the helper is a no-op (the persona scenario
|
|
* still asserts auth via the surrounding flow, but the role-specific
|
|
* coverage is left to the spec's own dedicated test blocks).
|
|
*
|
|
* The peer-exchange helper (`runPeerExchangeFlow`) is gated on the
|
|
* role declaring biber↔administrator interaction; its scope is the
|
|
* role-specific spec, not this helper module.
|
|
*/
|
|
|
|
async function runRoleInteraction(page, opts = {}) {
|
|
const { roleInteraction } = opts;
|
|
if (typeof roleInteraction !== "function") return;
|
|
await roleInteraction(page, opts);
|
|
}
|
|
|
|
/**
|
|
* Drive a peer exchange between biber and administrator on roles that
|
|
* support it (peer-to-peer messaging, comment threads, federation
|
|
* round-trips, …). The spec MUST pass a `peerExchange` callback that
|
|
* accepts two pages (biber's, administrator's) plus the credentials
|
|
* read from the env, and the callback drives the role-specific
|
|
* exchange. The helper provides the two browser contexts and tears
|
|
* them down on exit; the role-specific message/payload/assertion
|
|
* lives in the role's own spec.
|
|
*/
|
|
async function runPeerExchangeFlow(browser, opts) {
|
|
const { peerExchange, biberCreds, adminCreds, env } = opts;
|
|
if (typeof peerExchange !== "function") return;
|
|
|
|
const ctxBiber = await browser.newContext({ ignoreHTTPSErrors: true });
|
|
const ctxAdmin = await browser.newContext({ ignoreHTTPSErrors: true });
|
|
const pageBiber = await ctxBiber.newPage();
|
|
const pageAdmin = await ctxAdmin.newPage();
|
|
try {
|
|
await peerExchange({ pageBiber, pageAdmin, biberCreds, adminCreds, env });
|
|
} finally {
|
|
await ctxBiber.close().catch(() => {});
|
|
await ctxAdmin.close().catch(() => {});
|
|
}
|
|
}
|
|
|
|
module.exports = { runRoleInteraction, runPeerExchangeFlow };
|