> Asking people to write tests before they write code is like asking them to test-drive a new car before it even exists. This isn’t possible.

This is an incredibly bad analogy that really doesn't stand up. You can write tests before you write the implementation of them, to define how you want the end result of your program's interfaces to look. The rest of the article arguing the semantics behind calling them tests or specifications doesn't add anything but confusion to the testing discussion.

This:

> Calling tests specifications makes the concept more intuitively available in several ways.

Is entirely subjective.