* Adrian Howard <[EMAIL PROTECTED]> [2006-05-31T10:55:20]
> In short
> * Yes running one test method at a time is a sensible things to do.
> * No - there currently isn't a simple way of doing this
> * Good news - Ovid has submitted a patch to make it easy
> * Bad news - I've been too bone idle to a
Cool, it's manageable for now and our current testing -- using sometimes
large, monolithic Test::More .t files -- is no more flexible so there's no
loss in the move, but the flexibility will be appreciated when you get
around to it. Thanks for putting Test::Class together Adrian!
Andrew
On 5/31/0
Yeah, but it's so convenient to have my test classes reflect the classes of
my application. It makes it so easy to see what's going on when I name my
test methods the same thing as the methods in my application.
Andrew
On 5/31/06 10:47 AM, "A. Pagaltzis" <[EMAIL PROTECTED]> wrote:
> Hi Andrew,
>
[apologies to andrew for a dupe - didn't notice it went to perl-qa]
On 31 May 2006, at 14:35, Andrew Gianni wrote:
Let me start by admitting that I don't know a whole lot about xUnit
testing.
In fact, using Test::Class is really my first exposure to the idea, so
perhaps I'm asking for somethi
Hi Andrew,
* Andrew Gianni <[EMAIL PROTECTED]> [2006-05-31 15:40]:
> Is there an easy way to just run that one test method (as well
> as the startup, setup, teardown and shutdown methods) while I'm
> working on it rather than running the whole batch?
just write a base test class with all your sca
Let me start by admitting that I don't know a whole lot about xUnit testing.
In fact, using Test::Class is really my first exposure to the idea, so
perhaps I'm asking for something that doesn't make sense; please bear with
me in case I am.
Test::Class seems like a great idea for so many reasons, b
