go ahead... be a heretic | |
PerlMonks |
Re^3: Developing a module, how do you do it ?by BrowserUk (Patriarch) |
on Mar 02, 2012 at 04:44 UTC ( [id://957376]=note: print w/replies, xml ) | Need Help?? |
An alternative idea for having "non-boolean tests" directly in the source. What i don't like about it, is that it makes the source less readable : it becomes harder to search the interesting parts of the code. I think you got the wrong end of the stick about this. In the normal way of things, a module, Your::Thing.pm, looks like this:
And the tests live in a bunch of .t files. The "alternative idea" is that Your::Thing.pm looks like this:
You use the module in the normal way via use or require, and it works exactly as with the 'usual way' above. To run the tests, you type:
And the code that comes after the return 1 if caller; statement gets run. It really is as simple as that. And whilst the tests and code exist in the same file, the module code is above that line, and the tests are below it. There is no interleaving. Nothing is "less readable". Nothing is "harder to search" for. Indeed, maintenance is greatly simplified by having the code and tests within the same file. Try it. You'll never go back :) With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In Section
Seekers of Perl Wisdom
|
|