This is quite a loaded question so be gentle. :-)
I'm entertaining the idea of writing Test::CPANTS. During the development process, I want to be able to test my kwalitee rating (keeping it at 16) every time I get ready to release a new version of a module.
I've taken a look and Modules::CPANTS::Generator. Most of it looks reusable (like the individual test modules); but a good portion of it ::Generator seems to be based around the idea the I'm going to download a dist and use that. In the case of a Test::CPANTS, I'm really trying to work with the local lib/blib part of the dist to be tested.
This brings my to my question. Is it ok to use Test::MockObject for good (test.pl, t/*.t) AND evil; fooling Modules::CPANTS::Generator into using my local hacks to get it and CPANPLUS to not download things, but intead to use the local dist directory and a non-existant .tar.gz dist?
Ultimately it would be better to tweak Modules::CPANTS::Generator to work the way it is needed, but wheres the fun in that? :-)
In reply to Using Test::MockObject For Good And Evil by jk2addict
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |