Re:Ask HN: How can I convince a team member to try TDD
by rooam-dev on Wednesday April 03, 2019 @11:23AM
(#19564091)
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.
Re:Ask HN: How can I convince a team member to try TDD
by seanwilson on Friday April 05, 2019 @11:04AM
(#19583230)
> 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?
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?