Comments on: TDD: Design tests for failure

By: Coding: Reassessing what the debugger is for at Mark Needham

Coding: Reassessing what the debugger is for at Mark Needham — Fri, 20 Mar 2009 11:42:25 +0000

[...] It is usually quite easy to work out just from reading the error message we get from our testing framework where the problem is, and if it's not then we should look at writing our tests in a way that is more conducive for solving these types of problems. [...]

By: TDD: Test DRYness at Mark Needham

TDD: Test DRYness at Mark Needham — Fri, 30 Jan 2009 01:20:01 +0000

[...] I think certainly some of the reason for this is that we don't take as much care of our test code as we do production code but for me at least some of it is down to the fact that if we make our tests too DRY then they become very difficult to read and perhaps more importantly, very difficult to debug when there is a failure. [...]

By: Dew Drop - January 28, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - January 28, 2009 | Alvin Ashcraft's Morning Dew — Wed, 28 Jan 2009 13:47:49 +0000

[...] TDD: Design Tests for Failure (Mark Needham) [...]