testing-conventions

Use the formula "when/if [condition], [action/outcome]" so each name states a specific condition and result, like "returns 0 when map is empty". Avoid vague terms such as "handles", "correctly", or "properly", and omit the word "should".

Skip a test when the change adds no runtime behavior, when an existing gate like the compiler or linter already reproduces the failure condition, or when the test would only pin a value such as message wording or config contents that review already guards.

No. A permanent assertion that a deleted string or variant is absent encodes history rather than contract and guards no regression class. Verify the removal once as a pre-merge check, and write a positive test for the replacement behavior instead.

Use it.each when adjacent tests differ only in a small set of inputs and share a structurally identical body, so the variation reads as a table. Keep separate it blocks when the tests express genuinely distinct behavioral claims or have different assertion shapes.

Do not re-pin the new wording. Loosen the assertion to match only the durable fragment that identifies the behavior, or drop the assertion entirely if no behavior depends on the exact text.