http://search.cpan.org/dist/Test-Harness/lib/Test/Harness/TAP.pod implies
that if I want to skip all tests, I need something like this format:
1..0 # SKIP why not?
I've also noticed that all of the Test::Harness tests which exercise this
behavior use '1..0', even though this is only implied,
On Wed, Jan 24, 2007 at 04:43:52AM -0800, Ovid wrote:
http://search.cpan.org/dist/Test-Harness/lib/Test/Harness/TAP.pod implies
that if I want to skip all tests, I need something like this format:
1..0 # SKIP why not?
I've also noticed that all of the Test::Harness tests which exercise
--- Steve Peters [EMAIL PROTECTED] wrote:
My guess is that the number of test run may depend on things determined
after the point you decided to skip all the tests.
Sounds reasonable, but I also think it should be optional.
Cheers,
Ovid
--
Buy the book --
Has anyone ever used Test::More and Fatal together?
I have a test script, where each test builds upon the work of the previous
step (it's part of the Subversion Perl bindings test suite, and it checks
out files, makes changes to them, commits them, and so on).
If any of these tests fails I
On Jan 24, 2007, at 9:42 AM, Nik Clayton wrote:
Has anyone ever used Test::More and Fatal together?
I have a test script, where each test builds upon the work of the
previous step (it's part of the Subversion Perl bindings test
suite, and it checks out files, makes changes to them, commits
Chris Dolan wrote:
I don't like that very much. The implicit die() on test functions will
probably confuse subsequent readers of the code.
# Cause the listed functions to die on error
use Fatal qw(...);
Furthermore, I cannot believe that ALL of your tests are critical.
150 or so out
On Jan 24, 2007, at 1:25 PM, Nik Clayton wrote:
Chris Dolan wrote:
I don't like that very much. The implicit die() on test functions
will probably confuse subsequent readers of the code.
# Cause the listed functions to die on error
use Fatal qw(...);
Furthermore, I cannot believe
Ovid wrote:
http://search.cpan.org/dist/Test-Harness/lib/Test/Harness/TAP.pod implies
that if I want to skip all tests, I need something like this format:
1..0 # SKIP why not?
I've also noticed that all of the Test::Harness tests which exercise this
behavior use '1..0', even though this
James E Keenan wrote:
What with all the activity on this list in the last week (TAPx::Parser
about to morph into Test::Harness), it's all been more than I can keep
up with.
I would like to suggest that one or more or the hackerati who are
working on all these revisions to our core testing
On 1/24/07, Nik Clayton [EMAIL PROTECTED] wrote:
Has anyone ever used Test::More and Fatal together?
I have a test script, where each test builds upon the work of the previous
step (it's part of the Subversion Perl bindings test suite, and it checks
out files, makes changes to them, commits
On 1/23/07, James E Keenan [EMAIL PROTECTED] wrote:
I would like to suggest that one or more or the hackerati who are
working on all these revisions to our core testing functionality write
an article about what's happening.
I second that emotion.
--
Shawn Boyette
[EMAIL PROTECTED]
* Nik Clayton [EMAIL PROTECTED] [2007-01-24 16:45]:
Anyone used this approach before, or done anything similar?
I haven’t, but it seems perfectly reasonable if you can live with
Fatal’s annoying stack traces.
Another option would be something like
sub ensure { $_[ 0 ] or die broken
Hey folks,
Konobi pointed me at an interesting talk about writing customer
readable tests that were also executable. The video is from the
Google London Test Automation Conference. (The code is in some ugly
language... ;)
13 matches
Mail list logo
