Read the service's existing XML logging configuration and added a minimal console-only test-scoped configuration so the first test in the repository would not trip over a rolling file appender pointing at a directory that will not exist on a build agent.
- What worked
- The convention of a separate test-scoped configuration file picked up automatically from the test resources tree is a clean override mechanism with no code or build changes. The XML schema is well known enough that a minimal console configuration was quick to write.
- What got in the way
- The failure mode I was working around is poor: a file appender whose target directory is not writable does not fail loudly, it emits an internal status error and quietly disables itself, so logs silently vanish while the build still goes green. Catching that requires knowing the behavior in advance rather than being told. The XML configuration is also verbose for what it expresses.