When should you prefer CPAN testers and Kwalitee, and when should you avoid it?

When developing Perl modules, utilizing CPAN Testers and Kwalitee can significantly enhance the quality and reliability of the code. However, there are situations when one might prefer to avoid relying solely on these tools.

When to Prefer CPAN Testers

• When you want early feedback on the compatibility of your module across different Perl versions and operating systems.
• If your module has complex dependencies and you need to ensure they’re resolved correctly.
• When you're aiming for a wider audience and want to build credibility in the Perl community.

When to Prefer Kwalitee

• If you're focused on code quality and adherence to best practices.
• When you are working on a new module and want to ensure it meets minimum quality standards before release.
• If you need to identify areas of improvement in your code.

When to Avoid CPAN Testers and Kwalitee

• When your module is highly experimental or in a very early stage where rapid changes are being made.
• If your development environment is not representative of the broader community (e.g., custom configurations).
• When performance is more critical than compatibility, and you have specific benchmarks that may not align with general testing.