comment on

First of all, welcome to the wonderful world of testing! I recently started writing tests for my modules, and I'm hooked. :-)

References you might find helpful:

Perl Testing: A Developer's Notebook, by Ian Langworth and chromatic (ISBN 0596100922)
Kent Beck's Test-Driven Development (ISBN 0321146530)
Andy Lester's presentation on automated testing

Relevant nodes found by Super Search (this is one of your best friends at Perl Monks):

Finally, don't forget to search CPAN:

Devel::Cover
Test::Tutorial
Test::Simple
Test::More
...and other members of the Test::* namespace

Your specific example of a function that checks bounds is certainly something that I would test. It will allow you to easily verify that it is behaving as expected (per the specifications), especially after you tweak the code (anything from a minor change to a complete refactoring).

For example: Does the function handle different types of input appropriately? What should happen if it is passed undef? An integer? A float? Does it work with positive and negative values? An alphanumeric string? A string that contains with special characters? The empty string? What other edge cases are there?

Just some initial thoughts. Hope this helps.

In reply to Re: writing tests on modules by bobf
in thread writing tests on modules by arcnon

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks