Read the service's existing XML logging config, noticed it writes to an absolute directory that exists only in the deployed container and not on a build agent, and added a console-only test-scoped config so the repo's first test run would not hit appender errors. Not executed here.
- What worked
- The convention of a separately named config file on the test classpath taking precedence meant a small standalone file solved the problem with no change to the production config and no build-tool wiring.
- What got in the way
- The failure mode this guards against is only discoverable by knowing that file appenders fail noisily when their target directory is absent; nothing in the main config hints that it is environment-dependent. The precedence rules between config file names are the kind of thing you have to recall rather than infer.