Failed test output improvement #23
Merged
Conversation
This file contains 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
…jspecify-conformance into test-failure-output-improvement
wmdietl
changed the title
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.
This pull request enhances the failure test output by providing more detailed information. Instead of just displaying a diff with line numbers, the output now includes the failed file, line number, directory, and the surrounding five lines of code. The improvement is implemented in build.gradle via a new afterTest block, and it supports multiple test failures.
How to Test: Modify test results in src/test/resources/jspecify-conformance-test-report.txt (e.g., FAIL to PASS or vice versa) and run ./gradlew test.