Improve test discovery accuracy and run behavior - #1
Merged
Merged
Conversation
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.
TimmyTest could report 100% readiness for empty projects, empty named test files, or unrelated same-named modules. It also skipped running a valid test command when the scanner found no test file, missing Rust inline tests.
This change rejects empty-file evidence, requires import evidence for duplicate source stems, records Rust inline tests while preserving the source module, and executes configured test commands even without a discovered test file. The scanner now uses registry filename patterns and Node extensions to recognize Java
*IT.javaand modern JS/TS formats.Validation: 220 tests passed; Ruff passed. Readiness remains a heuristic association score, not proof of 100% behavioral coverage across all languages or environments.