[RUM-10753] Configure JUnit test tasks to log FAILED and STANDARD_ERROR events#3163
Merged
Conversation
Configure JUnit test tasks to log FAILED events and STANDARD_ERROR output, enabling visibility of diagnostic information (like Forge seeds) when tests fail in CI.
hamorillo
force-pushed
the
hector.morilloprieto/RUM-10753
branch
from
January 28, 2026 14:51
c3bb45b to
4d40871
Compare
|
🎯 Code Coverage 🔗 Commit SHA: 4d40871 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #3163 +/- ##
===========================================
- Coverage 70.98% 70.95% -0.02%
===========================================
Files 912 912
Lines 33548 33548
Branches 5640 5640
===========================================
- Hits 23811 23803 -8
- Misses 8158 8165 +7
- Partials 1579 1580 +1 🚀 New features to boost your workflow:
|
hamorillo
marked this pull request as ready for review
January 28, 2026 15:56
0xnm
approved these changes
Jan 28, 2026
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
3 participants
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 does this PR do?
This PR configures JUnit test tasks to log FAILED events and STANDARD_ERROR output, enabling visibility of diagnostic information (like Forge seeds) when tests fail in CI.
You can see an example of how it will look like here.
Motivation
Before this PR, when a test failed in CI, we didn’t have access to the Forge seed, so it wasn’t possible to reproduce the same test. This is especially important when dealing with flaky tests.
Additional Notes
This change will make the Gradle tasks more verbose, but in my opinion this is acceptable, since we’ll only look at the output when tests are failing, so it shouldn’t affect us much.
In addition, if you run
./local_ci.sh --test, you will see a number of tests that write toSTANDARD_ERRORor throw exceptions but still pass. It could be a good idea to take a look at them and verify that the tests are working as expected.Review checklist (to be filled by reviewers)