Hi!
I have a testsuite (PDF::FDF::Simple) that outputs a line with a
backslash at the end of a line (it's a test for backslash handling of
my module).
t/fdfparser_newline...1..10
ok 1 - setting up
ok 2 - parsing \ <--- HERE
ok 3 - parsing slash r
ok
- Original Message
From: Steffen Schwigon <[EMAIL PROTECTED]>
> Should I correct my test output or should TAP::Parser handle lines
> with trailing backslash differently?
I think that TAP::Parser's behavior is incorrect. The problem will be found in
the TAP::Parser::Grammar, specificall
I sometimes find that testing validation methods is annoying. They might look
something like this hideously contrived example:
sub _validate {
my $self =shift;
if ( $self->is_broken ) { throw_some_exception "we're broken" }
if ( $self->username ) { throw_another_exception "we gots
- Original Message
From: Ovid <[EMAIL PROTECTED]>
D'oh! You know, to make the behavior less mysterious, a better method name
could be chosen:
$some_class->mock_once(
is_broken => 1,
username => 'twinkletoes',
is_inflatable => 1
);
# is_broken tests
# twinkletoes tes
- Original Message
From: Adrian Howard <[EMAIL PROTECTED]>
> > As you can see, I called SUPER::startup instead of SUPER::setup.
> [snip]
>
> Not that it helps solve your problem - but I tend to use multiple
> setup routines rather than inheritance to add extra set up code to a
> class
Ovid wrote:
> And then, in my tests, I'll have something like:
>
> my $some_class = Test::MockModule->new($class);
> $some_class->mock( is_broken => 1 );
> # is_broken tests
> $some_class->unmock('is_broken');
> $some_class->mock( username => 'twinkletoes');
> # twinkletoes tests
> $some_cl
