CodeVetter · Repo Unpack · Testing signals
stylelint/stylelint
Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. The repository combines Jest rule schemas, integration tests, snapshot system tests, and selected node:test suites. The inspected tests demonstrate substantial behavioral specifications, but this bounded review does not establish exhaustive coverage or identify every untested branch.
- package.json configures Jest with jest-preset-stylelint, a Node environment, lib/system-tests/.changeset roots, V8 coverage, and global 90% thresholds; these are configured targets, not observed results.
- jest.setup.mjs exposes testRule and testRuleConfigs against the public lint API; setupAfterEnv clears emitted-warning state after each test.
- The inspected color-no-invalid-hex rule tests specify accepted alpha hex forms, quoted strings, URL fragments, and rejected hex values with exact start/end positions.
- standalone-fix tests specify fixed string output, config-enabled fixing, ignored inputs, and inline-disable behavior; edit-information tests specify replacement text/ranges and disableFix handling.
- standalone-cache tests inspect persisted cache entries, changed-file selection, config invalidation, and exclusion of error/warning files; their setup and cleanup perform filesystem mutations.
- CLI tests specify flag parsing; suppression tests mock process streams and check conflicting flags/stdin rejection; plugin tests exercise relative and absolute modules through PostCSS.
- System case 001 snapshots both filesystem and string-input APIs; snapshot preparation normalizes sources and removes private PostCSS results. The contributor guide explicitly describes system tests as real-use-case checks rather than comprehensive coverage.
- CI declares Node 20/22/24/26 across three OS families, a separate Node-24 coverage job, and an explicitly enabled Yarn PnP run; the default-gated PnP suite packages and installs dependencies, so ordinary Jest coverage does not imply it ran.