PA cockpit — tests¶
The Public Affairs cockpit is the most heavily tested surface in the product, and the only board with its own end-to-end suite.
These tests moved into a package
As of v2026.08.27 the cockpit lives in
@ronl/pa-cockpit, and its tests travelled
with it — they are no longer part of the packages/frontend suite. That is
why the frontend's own totals fell between v2026.08.23 and v2026.08.33
without anything being deleted.
Package: 41 files · 368 tests. Backend: 16 files · 533 tests in
src/pa-monitoring — the largest single area in the repository.
E2E: 2 specs · 7 tests, still in the frontend package.
Measured with npm test --workspace=@ronl/pa-cockpit on 29 August 2026 against
acc at 1e7fb19: 368 of 368 passing. Coverage 86.16 % statements ·
75.55 % branches · 83.46 % functions · 88.53 % lines.
The package suite¶
| File | Tests | Covers |
|---|---|---|
services/pa.api.test.ts |
66 | The cockpit's API client — the single largest test file in the package |
pages/public-affairs-v2/PaDataProvider.test.tsx |
21 | The context every cockpit screen consumes |
pages/public-affairs-v2/NotificationsPanel.test.tsx |
19 | Previously 0% — notifications were hardcoded to empty |
services/dossierbeheer.api.test.ts |
17 | The dossier API client |
components/PADashboardV2/dossierbeheer/Dossierbeheer.test.tsx |
17 | Dossier list, filters, status transitions |
pages/PADashboardV2.test.tsx |
15 | The page container and the host contract it requires |
components/PADashboardV2/PaSectionsRouter.test.tsx |
15 | The section-id grammar that replaced a fourteen-export surface |
pages/public-affairs-v2/Monitoring.test.tsx |
14 | Monitoring view |
pages/public-affairs-v2/Issuekaart.test.tsx |
14 | The issue map |
components/PADashboardV2/dossierbeheer/DossierEditor.test.tsx |
14 | Authoring a dossier |
services/mock-demo.store.test.ts |
11 | The mock store both hosts drive |
pages/public-affairs-v2/Kompas.test.tsx + kompas.test.ts |
20 | The kompas view and its pure data module |
components/PADashboardV2/dossierbeheer/MdEditor.test.tsx |
9 | The Markdown editor |
components/PADashboardV2/ZoekcriteriaSection.test.tsx |
9 | Saved-search criteria |
pages/public-affairs-v2/Vandaag.test.tsx |
8 | The 30-second start screen |
pages/public-affairs-v2/FeitenCijfers.test.tsx |
8 | Facts and figures |
components/PADashboardV2/dossierbeheer/DossierRow.test.tsx |
8 | Row rendering and actions |
pages/public-affairs-v2/AgendaView.test.tsx |
7 | The agenda |
components/PADashboardV2/PACommandPalette.test.tsx |
7 | The ⌘K palette |
By directory: pages/public-affairs-v2 119, services 94,
components/PADashboardV2/dossierbeheer 67, components/PADashboardV2
53, pages 15, modes 7, package root 10, test 3.
The guards that came with the extraction¶
Seven of the smallest files are not feature tests at all — they are structural guards protecting the package boundary, and they matter out of proportion to their test counts:
| File | Tests | Guards |
|---|---|---|
host.test.ts |
3 | That a host must configure the package before render, and fails with a named error if it does not |
index.test.ts |
2 | The public surface — so a re-export added by accident is caught |
modes/no-module-scope-modes.test.ts |
2 | That the unfiltered mode helpers stay unreachable, which is what keeps the demo's curation honest |
no-tailwind.test.ts |
1 | That no Tailwind utility class returns to the package |
no-host-protocol.test.ts |
1 | That no host session-storage key, IdP literal or router path is hardcoded back in |
The last one is the residue of a real defect class. The package had previously hardcoded five facts belonging to a host application; the guard exists so the seam cannot silently close again.
Two of these guards were themselves defective when written
The modes guard matched raw text, so a single line of documentation-shaped string could disarm the only rule covering dynamic imports — and a decoy function declared in an inner scope disarmed it for a whole file while compiling with zero type and lint errors. It now parses the source, and its accusing and excusing inputs are split so one can no longer feed the other. A guard is code, and needs its own red/green like anything else.
Backend¶
src/pa-monitoring — 533 tests across 16 files:
| File | Tests |
|---|---|
pa.routes.test.ts |
131 |
pa-dossiers.routes.test.ts |
96 |
curation.service.test.ts |
61 |
rules.test.ts |
38 (pure scoring) |
pa-dossiers.db.test.ts |
30 |
pa-monitoring.db.test.ts |
10 |
pa-cache.test.ts |
9 |
notifications.service.test.ts |
8 |
query-match.test.ts |
6 |
rss.test.ts |
4 |
Plus the TK, OB, EU, agenda and media source clients under
pa-monitoring/sources. Coverage: pa-monitoring 98.32%,
pa-monitoring/sources 97.07%.
E2E¶
Two Playwright specs, run with the same playwright.config.ts as the rest of
the frontend suite.
Measured 22 August 2026: 7 tests, 7 passed, 0 failed, 0 flaky, 0 skipped, 18.9s for the two together. The live spec was additionally run six consecutive times while chasing a flake, passing 2/2 each time in 7.3–11.7s.
| Spec | Tests | Covers |
|---|---|---|
pa-mock-journey.spec.ts |
5 | Mock mode driven against the real store with no mocking: curating moves the rail badges and the move survives a reload; an ignored signal stays ignored; Reset demodata restores every source to its fixture baseline; the reset control is offered in mock mode only; every signaalbron carries a watchlist orphan that can be linked to a dossier |
pa-live-authoring.spec.ts |
2 | Authoring against the live backend and a real database — a dossier and a zoekcriterium survive a genuine cold reload; live shows authored work while mock shows fixtures, from the same screen |
Why mock mode is worth an E2E suite¶
Every mock-mode defect found by hand in this window was invisible to the unit
suites by construction. They were not logic errors — a saved-search write that
was a bare return;, a confirm that built a new object and discarded it,
notifications hardcoded to empty, a resource fetched once at mount and never
again. Component tests mock the very seam that was broken, so they cannot see
any of it, and each one passed throughout.
Mock mode makes an unmocked end-to-end run affordable: the fixtures are deterministic and nothing depends on what happens to be in the database.
Why the live spec only covers authoring¶
Curation depends on TK OData, the EU RSS feed and the media aggregator, and TK alone measured 10s and 48s for the same query minutes apart — an assertion about signals arriving would be flaky by construction.
The live spec creates everything with a run-unique stamp and removes it again in
afterEach, including when the test fails part-way. Nothing global is reset:
pa:reset-data is a feature of the product, not test tooling.
Three lessons came out of building this suite
A throttled run that looks exactly like an outage, locator.count() not
auto-waiting, and a hand-written mock that passed vacuously. All three are
written up on Writing tests, because they generalise
well beyond this board.