ehoandClaude Sonnet 5
a7bf228ca8
The demo BSN, password, and DigiD login sequence were copy-pasted verbatim into all three specs; the diploma id #diploma-d1 was coupled to SeedData.cs's ordering by comment only, with no compile-time check if the seed shape changed. e2e/support/actors.ts names both: Actors.zorgverlener + loginAs() for the login sequence, SeedRefs.diplomaZonderPolicyVragen for the seed coupling (with the "why d1" reasoning attached to the name, not scattered across specs). Zero assertions changed — pure extract-and-rename of test setup. e2e test-isolation (the shared mutable backend) is a documented follow-up, not fixed here — see ADR-0006. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
32 lines
1.8 KiB
TypeScript
32 lines
1.8 KiB
TypeScript
import { expect, test } from '@playwright/test';
|
|
import { Actors, loginAs } from './support/actors';
|
|
|
|
// The dev-only `?scenario=error` toggle forces the scenario.interceptor to fail
|
|
// the request WITHOUT ever reaching the real HTTP transport (it substitutes a
|
|
// `throwError` in the rxjs pipe before `next(req)` runs) — so this is not
|
|
// observable as a browser network request. It IS observable as a real resource
|
|
// reload: `retry()` calls `resource.reload()`, which flips <app-async> back to
|
|
// its Loading (`aria-busy="true"`) state before failing again 400ms later.
|
|
// `currentScenario()` re-reads `window.location.search` on every call, not a
|
|
// one-shot value, so as long as the query param is still there, the retry
|
|
// genuinely re-runs and genuinely fails the same way — that's what's asserted
|
|
// here: a real reload cycle, not a no-op button.
|
|
test('dashboard error state renders, retry re-fetches (and fails again)', async ({ page }) => {
|
|
await loginAs(page, Actors.zorgverlener);
|
|
await expect(page).toHaveURL(/\/dashboard$/);
|
|
|
|
await page.goto('/dashboard?scenario=error');
|
|
// The dashboard has more than one independent <app-async> (profile,
|
|
// aantekeningen) — both fail under the blanket ?scenario=error, so this text
|
|
// legitimately appears more than once. Assert at least one, not exactly one.
|
|
const errorAlert = page.getByText('Er ging iets mis bij het laden van de gegevens.').first();
|
|
await expect(errorAlert).toBeVisible();
|
|
const retry = page.getByRole('button', { name: 'Opnieuw proberen' }).first();
|
|
await expect(retry).toBeVisible();
|
|
|
|
await retry.click();
|
|
// A real reload cycle: back to Loading (aria-busy) before failing again.
|
|
await expect(page.locator('[aria-busy="true"]').first()).toBeAttached({ timeout: 1_000 });
|
|
await expect(errorAlert).toBeVisible({ timeout: 5_000 });
|
|
});
|