4 ms·

Sure, but I have yet to find a better solution than TDD for big teams where team members come and go constantly.

• Deestan 10y ago
  "Branches aren't merged without peer approval" has sufficed plenty in my experience. Whether people code tests before thinking interfaces, before writing a prototype, before implementing, during the inevitable interface rewriting, after coding, after manual verification that it seems to work, or right before submitting the branch to review, doesn't matter as long as someone on the team looks over and sees that "yup, here are tests and they seem to cover the important parts, the interface makes sense, and the documentation is useful". Then people can do TDD, TLD, TWD or whatever they personally feel most productive with. Developers being happy and feeling in control of their own work does more for quality than enforcing a shared philosophy.