Reduce the number of 'Forgot to call init()' warnings during testing #152
Conversation
jonasbn
left a comment
There was a problem hiding this comment.
Looks good. I am pondering changing the test-suite to a Test::Class based implementation, so we can simplify the test suite and make the initial set up uniform
|
@jonasbn about the Test::Class idea to reduce setup: I think that's what TestUtil.pm in t/ is supposed to do (but apparently failing at). There's one failure mode (the one which is currently still generating the output) which we cannot solve by adding Test::Class, TestUtil or inclusion directly in the test scripts: the scripts generated automatically by Dist::Zilla to validate POD coverage. These scripts load the modules to inspect the resulting packages for "public" symbols bound to coderefs (i.e. available functions). Loading the code without initializing Log::Log4perl causes exactly this warning. My advocacy for using Log::Any is because it separates the concerns of log producers and log consumers. If there's no registered log consumer, there's no warning. There's just nothing. And from the perspective of anything in |
Description
However, if we were to use Log::ger or Log::Any, none of this would be an issue.
Type of change