ci: Generate test results XML of forge tests#18579
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #18579 +/- ##
===========================================
+ Coverage 75.38% 75.48% +0.09%
===========================================
Files 189 189
Lines 11239 11239
===========================================
+ Hits 8473 8484 +11
+ Misses 2620 2611 -9
+ Partials 146 144 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
smartcontracts
approved these changes
Dec 11, 2025
mds1
approved these changes
Dec 11, 2025
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.
Integrate forge test results with CCI for easier user feedback. It can be difficult to figure out which tests failed from reading the CCI console output, even after running a
just test-rerunjob.Here's an illustration of a sample failed test:
This PR also allows test insights on past test performance to be generated from the results by CCI.
Consideration
Contract testing In CI occurs in two steps: First to run all tests, which dumps test logs to the console, then a rerun on only the failed tests. The rerun is logged to a file and console output. This patch removes the console logging done by the first test execution. So users will no longer have access to the logs of forge tests that succeeded.