Personally, when I send code to CPAN and therefore CPAN Testers, I no longer rely on an exact number of warnings, because I've had issues with that: new versions of Perl may introduce new warnings, old versions of Perl may have warnings that you weren't expecting, and even different OSes might be different. Instead, I would suggest to either test for the presence of specific warnings that one's own code produces, or to test for the absence of specific warnings that should definitely not happen. Update: "No warnings at all" is fine if you're running one version of Perl on one OS, but once that changes, you can't necessarily rely on it. You can of course also try to modify your code to eliminate all warnings on all OSes and Perl versions, that would be optimal, but as you're discovering, that's not always feasible. Or, you can write your tests to expect those warnings, but that's of course not "no warnings at all".
In reply to Re: What is the proper way to suppress a warning in a test file?
by haukex
in thread What is the proper way to suppress a warning in a test file?
by nysus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |