Make test logging config easier to use#806
Merged
dennisvang merged 5 commits intodevelopfrom Nov 14, 2025
Merged
Conversation
and rename file so it is picked up automatically
dennisvang
force-pushed
the
maintenance/test-logging
branch
from
a09a15f to
db59e3b
Compare
dennisvang
added a commit
that referenced
this pull request
Dec 8, 2025
* include root logger AppenderRef, so we only need to change the log level, when required * rename test logging config file for clarity and conformance to log4j2 best practices
dennisvang
added a commit
that referenced
this pull request
Jan 29, 2026
* include root logger AppenderRef, so we only need to change the log level, when required * rename test logging config file for clarity and conformance to log4j2 best practices
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.
Current test logging config log4j2.xml does not produce any useful output at all during tests, except for the rudimentary test summaries from the test framework itself. Normal log messages, like those we see when running the app, are suppressed:
FAIRDataPoint/src/test/resources/log4j2.xml
Line 11 in 97a23a0
Normally this is good, because it prevents clutter, but it can also complicate "debugging."
This PR keeps the same default
level="off", but makes it easier to enable normal logging temporarily, when required:log4j2.xmltolog4j2-test.xml, to be more explicit, and more conformant to log4j autoconfigreplaces #803