On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger wrote:
> Currently I have a directory tree, and my testing consists of running
> prove on one .t file, a directory, or recursively over all. I don't
> seem to have a means of controlling the order of tests without using the
> shell. (i.e. "pr
Brett Sanger wrote:
I have some related tests. For example, to test the account management
of our LDAP administration tools on the website, I have a test to create
an account, test various edit options, then delete the account. (This
is testing the create and delete as well, so I don't want to
(insert off-topic grumblings about that "Munging Reply-To Considered
Harmful" and how I can't reply in one way to most lists anymore)
On Mon, Jul 18, 2005 at 09:44:25AM -0500, Andy Lester wrote:
> > shell. (i.e. "prove" will run the tests in whatever order it pleases.
> > "prove *" will run them
On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger ([EMAIL PROTECTED])
wrote:
> Currently I have a directory tree, and my testing consists of running
> prove on one .t file, a directory, or recursively over all. I don't
> seem to have a means of controlling the order of tests without using th
I've begun using perl's Test modules to do some unit testing on our code
and regression testing on some of our web applications.
Specificially, I'm using Test::More and prove.
However, I have some questions that aren't really addressed by the
documentation I've found thus far. These are basic q
