Does TDD mean not thinking about class design?

Question

I am making a role playing game for fun and attempting to use TDD while developing it. Many of the TDD examples I see focus on creating the test first, then creating objects tha

Answer 1

I think the balanced approach is the one you need to take. First model the classes of your domain, because without them, how do you even know what to test?

Then, you'll probably create stubs or shells of these classes, with mostly empty implementations, just to let you write some test structures.

Once that's done, your test cases will likely illuminate the need for new methods / classes / properties that weren't in the original design, but are discovered as being necessary.