Niek Otten
7b327a5601
The walking-skeleton happy path now drives the real S-12 flow: after submit, a behandelaar logs in to the behandel portal (medewerker realm), finds the registration in the werkbak by its reference, and clicks Goedkeuren — replacing the temporary domain admin endpoint. Treat the behandel origin as secure too, for its PKCE login. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
34 lines
1.7 KiB
TypeScript
34 lines
1.7 KiB
TypeScript
import { defineConfig, devices } from '@playwright/test';
|
|
|
|
// The e2e runs inside the compose network (infra/run-e2e-check.sh); baseURL defaults to the
|
|
// self-service service. Keep timeouts generous — the first navigation triggers the DigiD flow.
|
|
const baseURL = process.env.SELF_SERVICE_URL ?? 'http://self-service';
|
|
// The behandel portal is a second origin the happy path visits (staff approve from the werkbak);
|
|
// it needs the same insecure-origin-as-secure treatment as self-service for the PKCE login (below).
|
|
const behandelURL = process.env.BEHANDEL_URL ?? 'http://behandel';
|
|
|
|
export default defineConfig({
|
|
testDir: '.',
|
|
timeout: 90_000,
|
|
expect: { timeout: 15_000 },
|
|
retries: 1,
|
|
reporter: [['list']],
|
|
use: {
|
|
baseURL,
|
|
trace: 'on-first-retry',
|
|
// The portal is served over plain HTTP on a non-localhost origin (http://self-service) inside the
|
|
// compose network, so it is NOT a secure context — and Web Crypto (`crypto.subtle`) is undefined
|
|
// there. angular-auth-oidc-client needs SubtleCrypto to build the PKCE code challenge, so
|
|
// `authorize()` throws and the login redirect never fires (the login form never appears). In
|
|
// production the portal runs behind HTTPS, where this works. Rather than terminate TLS in the
|
|
// throwaway e2e stack, tell Chromium to treat this origin as secure — which faithfully emulates
|
|
// the production HTTPS context. This flag is only honoured by the full Chromium build (new
|
|
// headless), not Playwright's default headless-shell, so pin `channel: 'chromium'`.
|
|
channel: 'chromium',
|
|
launchOptions: {
|
|
args: [`--unsafely-treat-insecure-origin-as-secure=${baseURL},${behandelURL}`],
|
|
},
|
|
},
|
|
projects: [{ name: 'chromium', use: { ...devices['Desktop Chrome'] } }],
|
|
});
|