So what you want with testing is a general strategy that helps you eliminate possibilities like class instantiation errors, data type problems, etc. before moving on to so-called use cases. Cheesy example:

perl -e 'package foo; sub new { return bless {}} package main; my $new
+ = new foo(); use Test::More qw~no_plan~; diag(qq~High level prelimin
+ary testing...~); ok(1==1,qq~basic~); ok($new->isa(qq~foo~), qq~Is a 
+foo~); diag(qq~Use Case 1: Editing customers...~);'
[download]

If you follow a methodology where you start by eliminating the high level possibilities like dependencies, environment, and establishing that objects are in the proper states you will find that your tests themselves answer most (if not all) of your questions.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.