CodeVetter · Repo Unpack · Testing signals
biomejs/biome
Rust tests use the built-in harness plus insta snapshots and codegen-driven spec tests. Language crates keep tests/specs directories with input files and expectation comments. The JS API uses Vitest. GitHub Actions runs the Rust suite, parser conformance, and autofix. Coverage is dense on parsers, formatters, and lint rules, and thinner on daemon lifecycle and editor integration.
- Crate tests are invoked with cargo test or just test. A single crate is just test-crate <name>. Doctests are just test-doc. CONTRIBUTING.md documents these commands.
- Snapshot testing uses insta. Failing snapshots are reviewed with cargo insta accept, reject, or review. Formatter and lint tests often commit .snap files next to specs.
- Lint and assist fixtures follow a spec layout: a source file with biome-ignore or expect comments, generated by macros in biome_analyze and exercised by the language test harness. The testing-codegen skill documents quick_test and orphan checks.
- Parser tests compare against Test262, Babel, TypeScript, and Prettier corpora. The parser_conformance workflow fails the build when those suites regress.
- Fuzzing is a separate Cargo workspace under fuzz/ with cargo-fuzz targets for parsers and the formatter. It is not part of the default cargo test run.
- packages/@biomejs/js-api tests run under Vitest (the repo's stack tags and package scripts). They require a prior WASM or JSON-RPC build, so they do not run from cargo test alone.
- CLI behavior is tested in crates/biome_cli/tests with fixture projects (configuration, lint, format, migrate). These spawn the library entry rather than only unit-testing parsers.
- main.yml is the merge gate for Rust fmt, clippy, and test. autofix.yml regenerates bindings and schema when codegen drifts. lint_rule_docs.yml checks rule documentation.
- Formatter idempotency and Prettier comparison tests live beside biome_js_formatter and related crates. A format change is expected to update snapshots, not only assertions.
- Type-inference tests cover Salsa invalidation and module cycles in biome_js_type_info and biome_module_graph. Many syntax-only rules do not enable the type engine in their fixtures.
- Agents.md requires just f and just l before commit, plus the current crate's tests. User-facing changes also need a changeset under .changeset.