[davman]

Maybe TDD just isn't for him/her/other?

I prototype, then tests, then refactor and I know some people would be zealously against this style; demanding tests before everything. However my mind just doesn't work this way, I need to play with code to get ideas out of my head; coming up with relevant test cases takes a magnitude of time longer than making the prototype.

Now if your co-worker is not writing tests at all, this is a different matter, but as long as the code he writes is covered by a test suite in the end, what does it matter which order he/she does it in?

[rooam-dev]

The goal is to try it as a team. Having 2 devs on a project with different approaches won't be efficient.

The part I strongly believe is that before writing a piece of code I need to know what I am writing. Similar to a task/story, I need to have an acceptance criteria. Knowing to write a test means knowing what are you writing.

Thanks for your input.

[seanwilson]

> The part I strongly believe is that before writing a piece of code I need to know what I am writing. Similar to a task/story, I need to have an acceptance criteria. Knowing to write a test means knowing what are you writing.

Is there an existing problem in the team where people don't know what they're writing though?

[rooam-dev]

I think at a high level only. Try and see how it goes (write some code, execute it and see the results) could be improved.