fix: compile test sources in CodeQL build to increase Java scan coverage#168
Merged
Conversation
-x test skips compileTestJava, leaving ~100 test files unscanned (67% coverage). Switch to classes testClasses which compiles all main and test sources without running tests, targeting 100% file coverage. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
CodeQL was only scanning 213/316 Java files (67%) because
-x testin the Gradle build command also skipscompileTestJava, leaving all test sources untraced.Switching to
classes testClassescompiles all main and test sources across every module without running tests, targeting 100% file coverage.Before / After