Hi,
I have a test that looks like this:
ok(prepare_first(), "first prepared");
ok(test_first(), "first is working");
ok(prepare_second(), "second prepared");
ok(test_second(), "second is working");
That is, there is a phase where I setup the test environment
and then there is the actual test.
Matisse Enzer wrote:
> What's the current best practice for running a Perl program and getting
> a report of all the subroutine calls throughout the life of the program
> in the order in which they were called? (as opposed to something like
> Devel:Profile which lists all the subs, and how many tim
What's the current best practice for running a Perl program and
getting a report of all the subroutine calls throughout the life of
the program in the order in which they were called? (as opposed to
something like Devel:Profile which lists all the subs, and how many
times each sub was calle
(My first attempt to send this to perlqa bounced. Sorry if you're getting this
twice)
Announcement is here:
http://www.perlmonks.org/?node_id=628195
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Perl and CGI - http://users.easystreet.com/ovid/cgi_course/
Personal b
Michael Peters wrote:
Ricardo SIGNES wrote:
http://search.cpan.org/dist/Test-BinaryData/lib/Test/BinaryData.pm
Did you know that Test::LongString (despite the name) can handle binary
information too? Probably not as detailed as your diagnostics, but it
works
fairly well for seeing the differe
