Re^2: Strategy for conditional logging in tests

Replies are listed 'Best First'.
Re^3: Strategy for conditional logging in tests by Thilosophy (Curate) on Apr 02, 2008 at 04:30 UTC
I agree that having your code as a module or not does not make a big difference here, but you should be able to "diddle the logging to appropriate levels in the .t". Is it not possible to turn off logging from the test script for your negative tests, and then turn it back on for the others?	[reply]
Re^4: Strategy for conditional logging in tests by andreas1234567 (Vicar) on Apr 02, 2008 at 05:28 UTC
Well, I could always add functionality to toggle logging on or off and invoke it during tests, e.g. something simple like this: `sub log_toggle { ($_[0]) ? Log::Log4perl->appender_thresholds_adjust(7) : Log::Log4perl->appender_thresholds_adjust(-7); }` [download] However I think it's inelegant to add functionality to the script that is going to be used during testing only. I would rather that the test script did that alone.	[reply] [d/l]
Re^5: Strategy for conditional logging in tests by Thilosophy (Curate) on Apr 02, 2008 at 08:42 UTC
Maybe there is something I do not understand about Log4Perl, but could you not call `Log::Log4perl->appender_thresholds_adjust` from within your test script? The whole point of a configurable logging framework seems to be that you can configure logging from outside of the code that does the actual logging.	[reply] [d/l]
Re^6: Strategy for conditional logging in tests by andreas1234567 (Vicar) on Apr 02, 2008 at 09:29 UTC