Quality

Every counter says what it measured. Test cases are declared it() call sites, which equals the real figure only while nothing mints cases at runtime — so a parameterised form (it.each) or a call site inside a loop makes the generator print the file and line and label this figure a floor, and the page then reads “at least”. A spec file that yields zero cases still fails the build outright, because that is not a way of writing tests, it is what a broken comment-stripper looks like. “Documentation pages” counts routes that render one: the layout shell and the ** 404 both declare a component and neither is a page, so neither is in the 224. The version is read from projects/lib/package.json and cross-checked against the NGWR_VERSION constant, which is a separate copy; a mismatch fails the build rather than picking a side. The single runtime dependency is tslib.

All 9 of them have to be green before anything merges, and the publish job re-runs the lint and the library build again before it ships a tarball.

The trade is worth saying out loud: a green pull request says nothing about painted contrast or RTL overflow. If you are working on the library and you touch a token, a tint, or anything that paints text on an intent, run pnpm check:contrast yourself rather than waiting for the morning.

check:a11y

check:contrast

check:state-a11y

At least 5,430 cases across 303 spec files, and 229 of the 229 entry points own at least one. Read that second figure narrowly: it is file-level coverage of the catalog, not branch coverage of the code. Specs sit beside what they cover and assert the rendered DOM — roles, ARIA state and the .wr-* class names, which are public API because every component ships ViewEncapsulation.None. A spec that reaches into component internals passes straight through the kind of change that actually breaks people.

106 CDK test harness classes ship alongside, published from 72 ngwr/<name>/testing entry points, so your own tests can drive a select or a date picker without knowing its markup. Four entry points deliberately have none — three that draw into a canvas jsdom hands no context for, and a thin wrapper over the CDK's virtual scroller — and the reason is the same each time: every honest method would answer identically for a working component and a broken one.

Which is also the first hole. jsdom has no drawing context and no layout — every rect is 0×0 — so the canvas and WebGL components can never assert anything painted. All six install a recording context and five an error recorder besides, which carries their specs past the early return to frame counts, particle counts, a var(--wr-…) colour resolved against the host, gravity bringing a particle back down, and teardown. Painted output itself is not reachable, and neither is anything measured in pixels.

The second hole is mode coverage inside components that are covered.wr-table has column pinning, drag-reorder, grouping, tree rows, expandable rows, CSV export and a virtualized body on one host; a spec on the table says nothing about tree rows unless it exercises them, and not every spec does. A green suite here means no covered behaviour regressed — not that every behaviour is covered.

The third is classic-forms interop, and it is the one worth knowing about if you are weighing ngwr against a library that still ships a ControlValueAccessor. No accessor is created: Angular's NgModel / FormControlDirective drive the control's value or checked model directly. That bridge does not apply template validator directives — a required on an ngwr control produces no error and the form submits, so validators belong on the FormControl — and it ignores updateOn. Only some value controls are bound through the classic forms API in a spec: wr-checkbox and wr-select ([(ngModel)] and [formControl], plus the validator drop), wr-segmented (the same two bindings), wr-textarea ([(ngModel)], and [formControl] inside a form field), and wr-date-picker and wr-date-range-picker ([formControl]). The other reactive-forms specs drive native <input>s through WrValidators. Angular's own tests cover the bridge; the forms guide is where its semantics are written down.

That rule is the whole table. v12 moved three import paths, which is exactly what a codemod can move without reading the code around it. v10 and v11 changed painted colour, which no codemod can repair — and shipping an empty one would have told you your visual regressions were handled when they were not.

Both partials are deliberate. v12's other break — readI18nText() returning a Signal<string> — is not codemodded, because adding () means knowing which identifiers hold the result, and a wrong guess is a silent behaviour change. The type error names every call site instead. v14 rewrites its six renames and only reports the rest: opting a loading bar or a routed tab strip back into the router is a decision about a bundle, not a substitution, and the stricter date parsing has no token to detect. The migration guide documents every half, and every break back to v7.