I appreciate your attempt to clarify your position regarding Test::* -- and I think you make (by proxy) a very good point about the critical role of thinking about a problem rather than falling back on rote process.

However, what I would really like to see are some examples of the practices -- varied though they might be to each situation -- that you have used as an alternative.

The one CPAN module I found (Win32::Fmode) is rather spare on testing -- perhaps a symptom of Test::More frustration rather than an alternative.

I'd be interested in a meditation from you that lays out a few case studies along the lines of:


I think this would do a lot to educate us not just on your position -- which I think I understand better now and respect the core principles of -- but on your practices, which I'd genuinely like to learn from (without adopting slavishly, of course).


Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re: Testing methodology, best practices and a pig in a hut. by xdg
in thread Testing methodology, best practices and a pig in a hut. by BrowserUk

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":