Test as Specifications

Tests will always be incomplete, so they must be backed up with other mechanisms. I see this as a plus because I am a twisted mind.

One of the most dangerous things about a formal requirements specification is when people think that once they’ve written it, they are done communicating.

Communicating what a feature does based on requirements is not enough. More is needed to ensure that everything is shared.

Writing tests as specifications is not about changing the vocabulary but how you write the tests. Add the necessary specification that does not cover more than the need. Add tests to stress all functionality of the feature.

How the tests are written impacts system comprehension. Indirectly both the written and automated specifications become the source of truth of what is implemented in the system.