In my opinion,this debate has a lot to do with the language used,the tools ,the IDE... Java/C#/... can be heavily assisted with the right IDE,(test suit genera

In my opinion,this debate has a lot to do with the language used,the tools ,the IDE... Java/C#/... can be heavily assisted with the right IDE,(test suit generation,mock/stub generation...).So the cost of testing can be light,no matter how big the codebase is. In JS,or ruby.One actually has to write everything. Therefore,one would be less tempted to write heavily decoupled code with a huge graph of function constructors/classes. While ruby has a lot of sugar for a wide range of things,that's not javascript case. So in my opinion,the cost of testing and managing test suits is higher in languages such as javascript or ruby,therefore one is tempted to write as little code as possible,and sacrifice decoupling and sometime testability. In one hangout,DHH comes with a snippet of code,highly decoupled and testable.But does ruby encourage this kind of architecture?because it's more code to test and more testsuit to manage(and more tests to rewrite when refactoring). So isnt it more a language /tooling question than a TDD/mock not TDD/mock question?