RegisterExpectedError but got different error text

Feb 10, 2012 at 2:57 PM

When a test expects an error and a different error is raised, the test failure should include both the actual error message and the expected error message. That would make it much easy to spot the problem if the actual error is expected error but the text of the error doesn't exactly match the expected error.

 

I hit this yesterday while helping a coworker figure out why a test was failing. Turns out the problem was a close but not exact match on a time value. Had we seen both the expected an actual errors it would have been much faster to track down.

Mar 23, 2012 at 9:36 AM
Edited Mar 23, 2012 at 12:41 PM

 

ETA: April 7th or earlier.

Apr 1, 2012 at 4:03 AM

Implemented in V1.9.