"There's a bug in the module that is causing the test to fail after a certain test number."
But which test number? You wrote the tests ... which test is failing? The output will show you. Since you provided no code and no actual error output, i'll have to supply my own. I changed one value in one my modules and ran the test suite. This was the first error of 14 failed tests in two test files:
# Failed test 'north: correct HTML from method call'
# at ./t/07-theta-presets.t line 106.
If i look at that test file on line 106 i see:
is $table->north, $expected, "north: correct HTML from method call";
From here i have to go back to the definition of
north() and this was indeed the function that i changed a value in. No need for a debugger ... i know where the error is now. If i still can't see the error i can fall back on a debugger, but i find that emitting dumps of data to STDERR is faster for me. Read the test output -- if you can't determine where the problem is quickly then your tests are probably too complicated. Tests help to eliminate the need for a debugger if you have exhaustive coverage. Keep your tests simple and fast.
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)