chromatic wrote:
I use Module::Build (don't jerk your knee yet, Adam) so that I can easily
override 'make disttest' to run my author tests. I keep them in t/author/.
Build.PL for Test::MockObject should make it a little clearer:
http://search.cpan.org/src/CHROMATIC/Test-MockObject-1.08/Build.PL
There's no reason that someone who isn't me couldn't write something similar
for MakeMaker.
I prefer this approach because I don't have to remember any environment
variables to run all of my tests, and because my normal workflow before a
release runs the distribution tests.
Let me also suggest #3: revise the appropriate CPANTS tests to add Kwalitee
only if the static analysis tests do *not* run by default.
Me? Knee-jerk? NEVER! :)
As long as the following is true for tests unrelated to functionality,
I'm fine with any and every solution. The mechanism itself is probably
not important, we just want the following behaviour.
1. The author runs the tests
2. Automated testing systems run the tests
3. End-users installing the modules do NOT run the tests
Adam K
