For the benefit of passers by (Tek and I have just talked about this), that's not what I meant.

I believe in testing things that are likely to break. I believe in writing tests that are going to create value for the business/client/project, and eschewing all others (as each new test comes with a cost that can seriously add up over the lifetime of a project).

Having TDD'd the development of the feature, and being left with tests that ran reasonably quickly, documented the code's intent, and provided coverage against regression, it didn't occur to me to replace them with a couple of slower ones that are harder (which I read as "more expensive") to maintain.

I just need to get into the swing of writing cucumber that replaces TDD'd tests of the controller/view pairing, so I'm pulling in the same direction as the rest of the team…