fix(affected): exclude fixture paths from the test-file heuristic#36
Merged
Conversation
Paths under fixtures/, golden/, snapshots/, or testdata/ are no longer classified as tests solely because they sit under a test directory segment. Name-based patterns (test_*, *_test.*, *.test.*, *.spec.*) still apply. Co-authored-by: Cursor <cursoragent@cursor.com>
The fixture reclassification in is_test_file would have let fixture sources (intentionally uncalled) surface as dead-code candidates. dead_code now filters through a broader test-support predicate covering test and fixture directories.
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: escoffier-labs/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
affectedreported fixture sources as runnable tests:tests/fixtures/golden/mixed/src/bin/graphtrail-mcp.rscame back inaffected_testsbecauseis_test_filecounts any path with atests-like segment. Paths underfixtures/,fixture/,golden/,snapshots/, ortestdata/are now non-tests unless the file name itself matches a test-name pattern.testdataalso leaves the generic test-dir list (Go fixture convention).dead_codefiltered candidates with the same predicate, which would have let fixture symbols (intentionally uncalled) flood the candidate list - on this repo, 8 of 60 candidates. It now filters through a broader test-support predicate (tests or fixture dirs), keeping fixtures out of both reports for opposite reasons: not runnable tests foraffected, not dead code fordead_code.Why
An affected-test calibration bench over 17 historical commits of this repo (receipts in
benchmarks/affected-calibration/) surfaced the misclassification. The same bench returned a null result on traversal depth: recall identical at depth 1/3/5, so the depth default stays.Verification
cargo fmt --check,cargo clippy --all-targets --all-features -- -D warnings,cargo test --all-features,cargo build --release(Brigade receipts). E2E on the bench corpus:affected src/store/db.rs src/mcp.rsno longer lists the fixture file;dead-codecandidates drop 60 to 52 with 0 fixture paths.