Who starts with designing just the tests? I have no idea how this is an association with TDD. TDD is a feedback cycle, you write small increments of tests befo

Who starts with designing just the tests? I have no idea how this is an association with TDD. TDD is a feedback cycle, you write small increments of tests before writing a small bit of a code. You don't write a bunch of tests upfront, that'd be silly. The whole point is to integrate small amounts of learning as you go, which help guide the follow-on tests, as well as the actual implementation, not to mention questions to need to ask the broader business. Your DTD idea has been tried a lot in prior decades. In fact, as a student I was on one of those testing teams. It's a terrible idea, throwing code over a wall like that is a great way to radically increase the latency of communication, and to have a raft of things get missed. I have no idea why there's such common misconceptions of what TDD is. Maybe folks are being taught some really bad ideas here?