> driving poor design Would you care to expand on that? Let's say you are doing a classicist style TDD, where you try to mock at the highest level you can (fi

> driving poor design Would you care to expand on that? Let's say you are doing a classicist style TDD, where you try to mock at the highest level you can (files, network, UI) and then just exercise all the classes in between until you reach your target piece of code. Can you give me examples of TDD producing a bad design? I can see how a mockist approach, where you mock everything for each function you test, can be detrimental very quickly. But I have the feeling I'm mastering the classicist approach, and I don't see how tests can negatively impact design.