On 1 Jun 2007, at 06:38, chromatic wrote:
On Thursday 31 May 2007 19:08:27 Andy Armstrong wrote:
On 1 Jun 2007, at 02:09, brian d foy wrote:
I'll have some time next week if Andy doesn't beat me too it.
I'm having a rummage around now :)
chromatic: do you have a .perltidyrc you could send me? My muscle
memory keeps reaching for the perltidy hot key that would convert
your code to AndyPerl :)
I use -ci=4 -bl these days.
Not on Test::Kwalitee you didn't :)
What's peoples' view on this?
Test::Kwalitee currently exposes the known test types as methods. I can
make it delve into Module::CPANTS::Analyse to find the tests that are
actually available - but then what to do about the methods?
I could
* generate the methods dynamically based on the Kwalitee modules that
are installed
* generate only the current methods and add a new method test_against()
(or whatever) that provides access to any named Kwalitee test
* replace the generated methods with an AUTOLOAD handler
In the test_against() or AUTOLOAD scenarios I could then make Kwalitee
tests for which the module is unavailable skip automatically.
Thoughts?
--
Andy Armstrong, hexten.net
