I fail to see how the whole argument connects to you distaste of the Test:: modules. Is there anything in particular about the Test:: suite of modules that you don't like - or do you want to say that no test suite will be appropriate in 100% cases?
Re: Testing methodology, best practices and a pig in a hut.
Replies are listed 'Best First'.
Sorry, but I don't see where I am assuming anything - I am just asking a question. You say:
Anyone who's been around here for a while (and still bothers to read my posts), will know I have a distaste for Test::* suite of modules
and I am asking what is it that you don't like about them. Is it something specific to that set of modules, or is it something along the lines that there cannot be any good set of test modules? Or maybe you are using it as a metaphor for testing in general?
I'd love to see you elaborate on alternative techniques. Testing is often seen as a chore, and in the shop I work in, the problem is a blatant lack of testing (especially automated). More productive testing strategies might help push testing among peers, and that would be a good thing.
Better ideas for more productive testing are always welcome to me, but I'm not sufficiently trained or smart enough to derive more productive testing strategies from what you've written so far. I do use Smart::Comments, which I think you've mentioned, a little, but probably not as effective as I could. Also, there must be more to your techniques than using that?