testing

What problem does it solve? Tests often look green while proving nothing: titles promise more than bodies assert, negative assertions pass on typos, environment-switched tests count as coverage, and hard-coded fixture dates expire silently. This rule defines what actually counts as verification when editing test files and end-to-end suites. ## Core Features & Use Cases - Scenario-to-test binding: Names scenario ids in test titles, marks uncovered scenarios with reasons, and flags tests referencing nonexistent scenarios. - Pure-function discipline: Moves decisions out of components and services into pure functions checked by call, with time passed as a parameter instead of read from the machine clock. - End-to-end and snapshot rules: Covers stand seeding, browser raster determinism, snapshot reference handling, mask width pitfalls, and fail-open guard design. - Use Case: When adding a spec for an Angular component or a Playwright end-to-end test, load this rule to decide whether the check belongs in a unit test or an end-to-end path, how to title it, and which pitfalls (flaky waits, dead allowlist entries, silent skips) to avoid. ## Quick Start Load the testing rule before editing any spec file or end-to-end suite and follow its flow to decide how the new behavior must be verified.