Michael G Schwern wrote:
On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger wrote:
There are some tests that I would love to have abort as soon as they
fail. (If step 3 failed, then steps 4 and 5 are places I don't want to
go) Is there a way to make prove do this? I skimmed the
Test::Build
In article <[EMAIL PROTECTED]>, Brett Sanger
<[EMAIL PROTECTED]> wrote:
>> > > Test::Builder docs, in case I was going to have to roll my own
> > > prove-like tool, and didn't see an obvious call there either.
> >
> > Test::Manifest is the way to get them in a certain order.
>
> Ah, thanks. Is
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
