comment on

Welcome to the world of testing. (Not that I've been here all that long, but welcome.)

For the benefit of others reading your post, let me point out that effective test suites can be pretty basic. Typically, my tests are a line or two each -- less elaborate than the systematic checker you posted here. My test file may contain many of these cases, but each unit test is pretty basic. And as I find bugs, I fix the bug and cover myself by testing that case.

The XP approach of very simple unit tests, written before the code itself, testing basic and edge cases, is a strong strategy. If comprehensive, any code that passes the suite by definition matches the spec. In short, the tests document the common and unusual behavior of every object and method.

Surely whomever brings you gifts this time of year will be impressed by any use of testing at all, so that should bode well for you!

rkg

In reply to Re: Testing modules and methods while waiting for Santa by rkg
in thread Testing modules and methods while waiting for Santa by TVSET

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks