Styx's 100% coverage threshold went unenforced because CI never ran coverage
The core package of Styx had a 100% coverage threshold in its configuration, but CI never executed coverage checks, so nothing enforced it and the selector tests fell short. A pull request added the missing selector behaviour tests and a coverage command to the CI matrix. After the change, 664 tests pass with full statement and branch coverage. Some fallback branches were unreachable, so they were removed rather than covered with contrived tests, leaving observable results unchanged and the code smaller. The author concludes that a threshold only means something once CI runs the command that enforces it, and asks for 100% coverage only on pure logic packages such as state machines, policy and selectors, not UI code.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in