In TDD, should tests be written by the person who implemented the feature under test?

Posted by martin on Stack Overflow See other posts from Stack Overflow or by martin
Published on 2010-04-07T16:06:54Z Indexed on 2010/04/08 17:13 UTC
Read the original article Hit count: 175

We run a project in which we want to solve with test driven development. I thought about some questions that came up when initiating the project. One question was: Who should write the unit-test for a feature? Should the unit-test be written by the feature-implementing programmer? Or should the unit test be written by another programmer, who defines what a method should do and the feature-implementing programmer implements the method until the tests runs?
If I understand the concept of TDD in the right way, the feature-implementing programmer has to write the test by himself, because TDD is procedure with mini-iterations. So it would be too complex to have the tests written by another programmer?
What would you say? Should the tests in TDD be written by the programmer himself or should another programmer write the tests that describes what a method can do?

© Stack Overflow or respective owner

Related posts about software-engineering

Related posts about test-driven