Subject: TAP diagnostic syntax proposal
From: Michael G Schwern <[EMAIL PROTECTED]>
Date: Mon, 10 Jul 2006 10:19:03 -0700

}The PITA/TestBuilder2 BoF at YAPC::NA (which spent most of its time
}talking about TAP) sketched out a syntax for parsable TAP diagnostics.
}
}   not ok 2 - omg t3h sooper test!!1!
}   file:        foo.t
}   line:        45
}   description: omg t3h sooper test!!1!
}   got:         this
}   expected:    that
}   raw-test:    is( "this", "that", "omg t3h sooper test!!1!" );
}   x-THAC0:     16

I would be concerned about "got" or "expected" including embedded 
newlines, such as:

  is($mech->content,$expected_page,"Web page content matches what's expected");

even with a delimiter such as Ian suggested.  How would this handle that?

Also, would the raw test be pre-expanded?  That is, what would raw-test 
show for this?

  is($user,"testuser$id","Test user name correctly generated");

-Pete K
-- 
Pete Krawczyk
  perl at bsod dot net


Reply via email to