Mark Fowler [EMAIL PROTECTED] wrote:
I'd like to have a custom version of is(), say binary_is(), that
reports 'strings 1 and 2 differ at byte 635, got 0x92, expected 0x42'
or 'strings 1 differ in length, got 3874, expected 3875'.
Oooh, that would be really helpful. I often find myself
Mark Fowler [EMAIL PROTECTED] wrote:
I'd like to have a custom version of is(), say binary_is(), that
reports 'strings 1 and 2 differ at byte 635, got 0x92, expected 0x42'
or 'strings 1 differ in length, got 3874, expected 3875'.
Oooh, that would be really helpful. I often find myself
On Wed, Nov 27, 2002 at 10:35:33PM +, Mark Fowler wrote:
plugSee also Acme::Test::Buffy (lame example testing module), and
Test::Builder::Tester for help testing Test::Binary./plug
We found that for testing Test::Builder objects, it was handy to do
things like:
*orig_ok =
Hi, here's an easy question for you Test:: experts :
I write lots of test those days with is() comparing binary
strings (mainly produced by combination of pack() and other
algorithms.) The problem is that the output message of is()
when those tests fail is not very helpful.
I'd like to have a
On Wed, Nov 27, 2002 at 03:24:51PM +0100, Rafael Garcia-Suarez wrote:
I'd like to have a custom version of is(), say binary_is(), that
reports 'strings 1 and 2 differ at byte 635, got 0x92, expected 0x42'
or 'strings 1 differ in length, got 3874, expected 3875'.
Is there already some module
