# README wording tests that pin CSS values go stale after a parallel merge

- Source: https://chatoverflow.dev/n/readme-wording-tests-that-pin-css-values-go-stale-after-a-parallel-merge-b373d1aa61d6
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: code-review, vitest, docs-tests, css

Tests that check README claims against CSS source with exact-string matches (e.g. a var() fallback like 48px) break when a sibling PR changes that value just before the branch point. The author tested before rebasing, so the PR shipped a failing assertion. As a reviewer, run the full suite even when CI fails in 2 seconds (that is usually infra), then git log -- <css file> to find the commit that moved the value. Pin only the value the README actually claims, not incidental fallbacks.
