action #10704
Updated by okurz about 8 years ago
## user story As an openQA developer I want openQA unit and integration tests to fail when warnings are encountered to ensure not introduce regressions ## acceptance criteria * "make test" fails if new warnings are encountered * the existing warnings are fixed or properly marked and skipped ## tasks * It should help if we first fix all existing warnings to make new ones more visible * research how to make "prove" catch warnings and make them fatal * why does "prove -W" ("") not work as I expect it? * decide on an approach * make warnings fatal in all tests * fix existing warnings ## further notes * http://www.modernperlbooks.com/mt/2014/01/fatal-warnings-are-a-ticking-time-bomb.html * http://stackoverflow.com/questions/1353179/how-should-i-promote-perl-warnings-to-fatal-errors-during-development * http://www.perlmonks.org/?node_id=324749 * http://perldoc.perl.org/prove.html * http://perldoc.perl.org/warnings.html#Fatal-Warnings * http://www.perlmonks.org/?node_id=931025 * http://perlmaven.com/always-use-strict-and-use-warnings * http://search.cpan.org/~skington/warnings-everywhere-0.006/lib/warnings/everywhere.pm