Project Management

A Learning Process: Re-doing CoR part 1

From the Sustainable Test-Driven Development Blog
Test-driven development is a very powerful technique for analyzing, designing, and testing quality software. However, if done incorrectly, TDD can incur massive maintenance costs as the test suite grows large. This is such a common problem that it has led some to conclude that TDD is not sustainable over the long haul. This does not have to be true. It's all about what you think TDD is, and how you do it. This blog is all about the issues that arise when TDD is done poorly—and how to avoid them.

About this Blog


Recent Posts


The Importance of Test Failure

Mock Objects, Part 1

Mock Objects, Part 2

Mock Objects, Part 3

We're writing this blog for several reasons:

  1. To work out the intellectual material for the book we're writing
  2. To provide value to our community as quickly as possible
  3. To get feedback from our readers as soon as possible (validation-centric)

However, we're also finding that the process of creating each blog and each podcast is, in and of itself, a learning process.  In recording the podcast for the Testing the Chain of Responsibility, Part 1 blog we realized that we'd actually done it wrong. [1]

In that blog we said "The same mock can be used to test each Handler."  The problem with that is the redundancy; we'll be testing the delegation issues in each handler, and those tests will all be duplicates of each other.

So, stay tuned for Testing the Chain of Responsibility Part 1, Redux.

We learn from you, but we also learn from ourselves. :) 


Posted on: February 11, 2021 08:00 AM | Permalink

Comments (0)

Please login or join to subscribe to this item

Please Login/Register to leave a comment.


"A nod's as good as a wink to a blind bat"

- Eric Idle, Monty Python's Flying Circus