Timeline for Can TDD be suitable for a small team with overlapping but not identical domain knowledge
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 20, 2023 at 13:14 | comment | added | Doc Brown | ... and bakes these ideas into the test. There have been experiments in pair programming in making this a ping-pong game for two persons (one dev writes a test, another the functionality to fulfill the test, then they switch roles, see openpracticelibrary.com/practice/ping-pong-programming), maybe it works for some people, but AFAIK they haven't become really popular). | |
| Oct 20, 2023 at 13:08 | comment | added | Doc Brown | TDD is an implementation technique, a tool which can (and usually should) be used by one person. When dev A is going to write a new function, he/she first writes a test which shapes the new functions parameters, then A implements a little part of the function, and runs the test to try it out. Then A might change the test bit or add a new one, add some new functionality, runs the test again, refactors the function and/or the test. This is a design process where a creator of a function externalizes his/her idea about how a function should behave immediately while writing the function ... | |
| Oct 20, 2023 at 11:02 | vote | accept | user8469759 | ||
| Oct 20, 2023 at 10:49 | answer | added | Thomas Owens♦ | timeline score: 7 | |
| Oct 20, 2023 at 9:22 | comment | added | Rik D | Writing a small test is supposed to take minutes at max. Same for writing the code to make the test pass. When you want to include multiple devs, let them pair/mob program. They can still follow TDD practices, but without the hassle code handover would cause. | |
| Oct 20, 2023 at 9:16 | comment | added | Euphoric | That is gross misunderstanding of TDD. In TDD, the test is written immediatelly before code is written. The whole TDD cycle (test, code, refactor) should take less than few minutes. The two rules of TDD are : Never write production code without failing test and Never write more test code than is necessary to fail. Batching out failign tests or having someone else write the tests goes straight against TDD principles. | |
| Oct 20, 2023 at 8:36 | answer | added | bdsl | timeline score: 8 | |
| Oct 20, 2023 at 6:58 | history | asked | user8469759 | CC BY-SA 4.0 |