How to use test driven development without screwing program structure up?

If test driven development requires that the program is restructured so that it can be tested, for instance a class may be broken into two classes, what techniques can be used to make sure that the program structure does not become impossible to understand? Is there a set of maxims for making a object-oriented program compatible with TDD?