use Perl

• That's the Point! (Score:1)

  by chromatic (983)

  Unless I'm tremendously misunderstanding your point, the Test::Builder singleton exists to make that possible. That's why we wrote it that way. As long as you can translate things into calls to Test::Builder::ok() somehow, it ought to work.
  • Re:That's the Point! (Score:1)

    by petdance (2468)

    Here's an example: I've got a module Foo that asserts regularly. Now, I go and run some tests against Foo's functions, including those that assert.

    package Foo;
    
    sub wango {
      my $self = shift;
      assert_isa( $self, 'Foo' );
      # Now do my object magic
    }

    but then, I also want to test that, so in my .t file:

    my $foo = new Foo;
    isa( $foo, 'Foo' );
    my $n = $foo->wango;
    ok( $n, 'wango returned non-zero' );

    In this case, the singleton would be used by (in order) isa, assert_isa and ok. Test::Builder's

    --
    

    --
    xoa
    • Re:That's the Point! (Score:1)

      by chromatic (983)

      Oh, I think I understand. Writing tests for a module that uses Test::Builder can be tricky, yes. That's why there's Test::Builder::Tester [cpan.org].
      • Re:That's the Point! (Score:1)

        by petdance (2468)

        Writing tests for a module that uses Test::Builder can be tricky, yes.

        If we made Carp::Assert use Test::Builder, then EVERY module that uses Carp::Assert (which I hope would be many) would suddenly become one of those tricky modules and people would have to use T::B::T. :-(

        --
        

        --
        xoa