Curtis "Ovid" Poe > TAPx-Parser > TAPx::Parser

Download:
TAPx-Parser-0.50_07.tar.gz

Dependencies

Annotate this POD

Module Version: 0.50_07   Source  

NAME ^

TAPx::Parser - Parse TAP output

VERSION ^

Version 0.50_07

good_plan

Deprecated. Use is_good_plan instead.

SYNOPSIS ^

    use TAPx::Parser;

    my $parser = TAPx::Parser->new( { source => $source } );
    
    while ( my $result = $parser->next ) {
        print $result->as_string;
    }

DESCRIPTION ^

TAPx::Parser is designed to produce a proper parse of TAP output. It is ALPHA code and should be treated as such. The interface is now solid, but it is still subject to change.

For an example of how to run tests through this module, see the simple harnesses examples/.

METHODS ^

Class methods

new

 my $parser = TAPx::Parser->new(\%args);

Returns a new TAPx::Parser object.

The arguments should be a hashref with one of the following keys:

The following keys are optional.

Instance methods

next

  my $parser = TAPx::Parser->new( { source => $file } );
  while ( my $result = $parser->next ) {
      print $result->as_string, "\n";
  }

This method returns the results of the parsing, one result at a time. Note that it is destructive. You can't rewind and examine previous results.

If callbacks are used, they will be issued before this call returns.

Each result returned is a subclass of TAPx::Parser::Result. See that module and related classes for more information on how to use them.

run

  $parser->run;

This method merely runs the parser and parses all of the TAP.

INDIVIDUAL RESULTS ^

If you've read this far in the docs, you've seen this:

    while ( my $result = $parser->next ) {
        print $result->as_string;
    }

Each result returned is a TAPx::Parser::Result subclass, referred to as result types.

Result types

Basically, you fetch individual results from the TAP. The five types, with examples of each, are as follows:

Each result fetched is a result object of a different type. There are common methods to each result object and different types may have methods unique to their type. Sometimes a type method may be overridden in a subclass, but its use is guaranteed to be identical.

Common type methods

type

Returns the type of result, such as comment or test.

as_string

Prints a string representation of the token. This might not be the exact output, however. Tests will have test numbers added if not present, TODO and SKIP directives will be capitalized and, in general, things will be cleaned up. If you need the original text for the token, see the raw method.

raw

Returns the original line of text which was parsed.

is_plan

Indicates whether or not this is the test plan line.

is_test

Indicates whether or not this is a test line.

is_comment

Indicates whether or not this is a comment.

is_bailout

Indicates whether or not this is bailout line.

is_unknown

Indicates whether or not the current line could be parsed.

is_ok

  if ( $result->is_ok ) { ... }

Reports whether or not a given result has passed. Anything which is not a test result returns true. This is merely provided as a convenient shortcut which allows you to do this:

 my $parser = TAPx::Parser->new( { source => $source } );
 while ( my $result = $parser->next ) {
     # only print failing results
     print $result->as_string unless $result->is_ok;
 }

plan methods

 if ( $result->is_plan ) { ... }

If the above evaluates as true, the following methods will be available on the $result object.

plan

  if ( $result->is_plan ) {
     print $result->plan;
  }

This is merely a synonym for as_string.

tests_planned

  my $planned = $result->tests_planned;

Returns the number of tests planned. For example, a plan of 1..17 will cause this method to return '17'.

directive

 my $directive = $result->directive; 

If a SKIP directive is included with the plan, this method will return it.

 1..0 # SKIP: why bother?

explanation

 my $explanation = $result->explanation;

If a SKIP directive was included with the plan, this method will return the explanation, if any.

commment methods

 if ( $result->is_comment ) { ... }

If the above evaluates as true, the following methods will be available on the $result object.

comment

  if ( $result->is_comment ) {
      my $comment = $result->comment;
      print "I have something to say:  $comment";
  }

bailout methods

 if ( $result->is_bailout ) { ... }

If the above evaluates as true, the following methods will be available on the $result object.

explanation

  if ( $result->is_bailout ) {
      my $explanation = $result->explanation;
      print "We bailed out because ($explanation)";
  }

If, and only if, a token is a bailout token, you can get an "explanation" via this method. The explanation is the text after the mystical "Bail out!" words which appear in the tap output.

unknown methods

 if ( $result->is_unknown ) { ... }

There are no unique methods for unknown results.

test methods

 if ( $result->is_test ) { ... }

If the above evaluates as true, the following methods will be available on the $result object.

ok

  my $ok = $result->ok;

Returns the literal text of the ok or not ok status.

number

  my $test_number = $result->number;

Returns the number of the test, even if the original TAP output did not supply that number.

description

  my $description = $result->description;

Returns the description of the test, if any. This is the portion after the test number but before the directive.

directive

  my $directive = $result->directive;

Returns either TODO or SKIP if either directive was present for a test line.

explanation

  my $explanation = $result->explanation;

If a test had either a TODO or SKIP directive, this method will return the accompanying explantion, if present.

  not ok 17 - 'Pigs can fly' # TODO not enough acid

For the above line, the explanation is not enough acid.

is_ok

  if ( $result->is_ok ) { ... }

Returns a boolean value indicating whether or not the test passed. Remember that for TODO tests, the test always passes.

Note: this was formerly passed. The latter method is deprecated and will issue a warning.

is_actual_ok

  if ( $result->is_actual_ok ) { ... }

Returns a boolean value indicating whether or not the test passed, regardless of its TODO status.

Note: this was formerly actual_passed. The latter method is deprecated and will issue a warning.

is_unplanned

  if ( $test->is_unplanned ) { ... }

If a test number is greater than the number of planned tests, this method will return true. Unplanned tests will always return false for is_ok, regardless of whether or not the test has_todo (see TAPx::Parser::Result::Test for more information about this).

has_skip

  if ( $result->has_skip ) { ... }

Returns a boolean value indicating whether or not this test had a SKIP directive.

has_todo

  if ( $result->has_todo ) { ... }

Returns a boolean value indicating whether or not this test had a TODO directive.

Note that TODO tests always pass. If you need to know whether or not they really passed, check the is_actual_ok method.

in_todo

  if ( $parser->in_todo ) { ... }

True while the most recent result was a TODO. Becomes true before the TODO result is returned and stays true until just before the next non- TODO test is returned.

TOTAL RESULTS ^

After parsing the TAP, there are many methods available to let you dig through the results and determine what is meaningful to you.

plan

 my $plan = $parser->plan;

Returns the test plan, if found.

passed

 my @passed = $parser->passed; # the test numbers which passed
 my $passed = $parser->passed; # the number of tests which passed

This method lets you know which (or how many) tests passed. If a test failed but had a TODO directive, it will be counted as a passed test.

failed

 my @failed = $parser->failed; # the test numbers which failed
 my $failed = $parser->failed; # the number of tests which failed

This method lets you know which (or how many) tests failed. If a test passed but had a TODO directive, it will be counted as a failed test.

actual_passed

 # the test numbers which actually passed
 my @actual_passed = $parser->actual_passed;

 # the number of tests which actually passed
 my $actual_passed = $parser->actual_passed;

This method lets you know which (or how many) tests actually passed, regardless of whether or not a TODO directive was found.

actual_ok

This method is a synonym for actual_passed.

actual_failed

 # the test numbers which actually failed
 my @actual_failed = $parser->actual_failed;
 # the number of tests which actually failed
 my $actual_failed = $parser->actual_failed;

This method lets you know which (or how many) tests actually failed, regardless of whether or not a TODO directive was found.

todo

 my @todo = $parser->todo; # the test numbers with todo directives
 my $todo = $parser->todo; # the number of tests with todo directives

This method lets you know which (or how many) tests had TODO directives.

todo_passed

 # the test numbers which unexpectedly succeeded
 my @todo_passed = $parser->todo_passed;
 # the number of tests which unexpectedly succeeded 
 my $todo_passed = $parser->todo_passed;

This method lets you know which (or how many) tests actually passed but were declared as "TODO" tests.

todo_failed

  # deprecated in favor of 'todo_passed'.  This method was horribly misnamed.

This was a badly misnamed method. It indicates which TODO tests unexpectedly succeeded. Will now issue a warning and call todo_passed.

skipped

 my @skipped = $parser->skipped; # the test numbers with SKIP directives
 my $skipped = $parser->skipped; # the number of tests with SKIP directives

This method lets you know which (or how many) tests had SKIP directives.

has_problems

  if ( $parser->has_problems ) {
      ...
  }

This is a 'catch-all' method which returns true if any tests have currently failed, any TODO tests unexpectedly succeeded, or any parse errors.

is_good_plan

  if ( $parser->is_good_plan ) { ... }

Returns a boolean value indicating whether or not the number of tests planned matches the number of tests run.

Note: this was formerly good_plan. The latter method is deprecated and will issue a warning.

And since we're on that subject ...

tests_planned

  print $parser->tests_planned;

Returns the number of tests planned, according to the plan. For example, a plan of '1..17' will mean that 17 tests were planned.

tests_run

  print $parser->tests_run;

Returns the number of tests which actually were run. Hopefully this will match the number of $parser->tests_planned.

exit

  $parser->exit;

Once the parser is done, this will return the exit status. If the parser ran an executable, it returns the exit status of the executable.

wait

  $parser->wait;

Once the parser is done, this will return the wait status. If the parser ran an executable, it returns the wait status of the executable. Otherwise, this mererely returns the exit status.

parse_errors

 my @errors = $parser->parse_errors; # the parser errors
 my $errors = $parser->parse_errors; # the number of parser_errors

Fortunately, all TAP output is perfect. In the event that it is not, this method will return parser errors. Note that a junk line which the parser does not recognize is not an error. This allows this parser to handle future versions of TAP. The following are all TAP errors reported by the parser:

CALLBACKS

As mentioned earlier, a "callback" key may be added may be added to the TAPx::Parser constructor. If present, each callback corresponding to a given result type will be called with the result as the argument if the run method is used. The callback is expected to be a subroutine reference (or anonymous subroutine) which is invoked with the parser result as its argument.

 my %callbacks = (
     test    => \&test_callback,
     plan    => \&plan_callback,
     comment => \&comment_callback,
     bailout => \&bailout_callback,
     unknown => \&unknown_callback,
 );
 
 my $aggregator = TAPx::Parser::Aggregator->new;
 foreach my $file ( @test_files ) {
     my $parser = TAPx::Parser->new(
         {
             source    => $file,
             callbacks => \%callbacks,
         }
     );
     $parser->run;
     $aggregator->add( $file, $parser );
 }

Callbacks may also be added like this:

 $parser->callback( test => \&test_callback );
 $parser->callback( plan => \&plan_callback );

There are, at the present time, seven keys allowed for callbacks. These keys are case-sensitive.

1 test

Invoked if $result->is_test returns true.

2 plan

Invoked if $result->is_plan returns true.

3 comment

Invoked if $result->is_comment returns true.

4 bailout

Invoked if $result->is_unknown returns true.

5 unknown

Invoked if $result->is_unknown returns true.

6 ELSE

If a result does not have a callback defined for it, this callback will be invoked. Thus, if all five of the previous result types are specified as callbacks, this callback will never be invoked.

7 ALL

This callback will always be invoked and this will happen for each result after one of the above six callbacks is invoked. For example, if Term::ANSIColor is loaded, you could use the following to color your test output:

 my %callbacks = (
     test => sub {
         my $test = shift;
         if ( $test->is_ok && not $test->directive ) {
             # normal passing test
             print color 'green';
         }
         elsif ( !$test->is_ok ) {    # even if it's TODO
             print color 'white on_red';
         }
         elsif ( $test->has_skip ) {
             print color 'white on_blue';
 
         }
         elsif ( $test->has_todo ) {
             print color 'white';
         }
     },
     ELSE => sub {
         # plan, comment, and so on (anything which isn't a test line)
         print color 'black on_white';
     },
     ALL => sub {
         # now print them
         print shift->as_string;
         print color 'reset';
         print "\n";
     },
 );

See examples/tprove_color for an example of this.

TAP GRAMMAR ^

If you're looking for an EBNF grammar, see TAPx::Parser::Grammar.

BACKWARDS COMPATABILITY ^

The Perl-QA list attempted to ensure backwards compatability with Test::Harness. However, there are some minor differences.

Differences

ACKNOWLEDGEMENTS ^

All of the following have helped. Bug reports, patches, (im)moral support, or just words of encouragement have all been forthcoming.

AUTHOR ^

Curtis "Ovid" Poe, <ovid@cpan.org> Andy Armstong, <andy@hexten.net>

BUGS ^

Please report any bugs or feature requests to bug-tapx-parser@rt.cpan.org, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=TAPx-Parser. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.

Obviously, bugs which include patches are best. If you prefer, you can patch against bleed by via anonymous checkout of the latest version:

 svn checkout http://svn.hexten.net/tapx

COPYRIGHT & LICENSE ^

Copyright 2006 Curtis "Ovid" Poe, all rights reserved.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

syntax highlighting: