Re: TODO blocks for Test::XML, and in general

[MidLifeXis]

Can you add the actual output and what you expect the output to be? For example, on my machine, I get:

#$ perl -MTest::More -e 'plan "no_plan";TODO:{local $TODO="foo bar"; f
+ail("blog");}'
not ok 1 - blog # TODO foo bar
#   Failed (TODO) test 'blog'
#   at -e line 1.
1..1

This is a valid TODO test (and a harness would mark the test suite as passed, even though it looks like it has failed). I don't have Test::XML::XPath installed, so just in case this is more of a case of improper expectations, pasting what you are seeing might help.

[nglenn]

I updated it. Running with prove shows that the test causes the entire test suite to fail.

[MidLifeXis]

Stupid question, but does my snippet above emit a TODO test?

I also rebuilt the like_xpath routine after removing the lines making use of the XPath parser (see below). What output do you get from it?

use strict;
use warnings;

use Carp;
use Test::More;
use Test::Builder;

sub like_xpath {
    my ($input, $statement, $test_name) = @_;
    die "usage: like_xpath(xml,xpath[,name])"
      unless $input && $statement;

    my $Test = Test::Builder->new;
    my $ok = eval {
        # Hardcode a failure
        return 0;
    };
    if ($@) {
       $Test->ok( 0, $test_name );
       $Test->diag( "  Parse Failure: $@" );
       return 0;
    } else {
       ok( $ok, $test_name );
       unless ( $ok ) {
           diag ( "           input: $input" );
           diag ( "  does not match: $statement" );
       }
       return $ok;
    }
}

plan tests=>1;
TODO: {
   local $TODO = 'testing todo block';
   like_xpath('<xml-bad/>', '/xml', 'test test');
}

[nglenn]

Your snippet and your edited version both result in TODO tests, and a passing grade for the test suite. Don't know why...