Use of the word "Test" considered harmful

Brian Marick's recent blog posts point out that the word "test" is too loose to be useful to TDD programmers. He suggests change detectors for backward-looking "programmer tests" - those that alert us when we have significantly changed the structure of the software - and code-guiding examples for forward-looking "programmer tests"- those that provide a specification of sorts for the code that we are about to write. And perhaps controversially he questions whether a single technology - be it JUnit or NUnit or whatever - can meet the needs of both detecting changes and guiding progress. Interesting.