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
Here's an interesting way of depicting the statements that are likely
to have cause test failures:
http://www.cc.gatech.edu/aristotle/Tools/tarantula/
Tarantula displays each source code statement using color models
that reflect its relative success rate of its execution by the test
