I can heartily recommend reading "Growing Object Oriented Software: Guided
by Tests". (
).
It walks you through the entire process, and unlike alot of literature
doesn't shy away from some of the more "hairy" problems. The entire book
is pretty much an answer to your question
On Mon, Jan 21, 2013 at 6:05 PM, Matteo Vaccari <vaccari@...> wrote:
**
On Mon, Jan 21, 2013 at 6:47 PM, sh shvfn@...> wrote:
Dear Listables,
...
For example I expect to end up with
- an engine class,
- a scene or context
- a renderer,
- an event- or signal/slot-system,
- an entity/component system
- etc, etc.
When I now start to write my first tests, I guess I start with the
engine class.
... I would not start with that. I would more likely start with the test
of a simple behaviour of the completed system. Then I'd build just as
little as possible to make the test pass.
Matteo
[Non-text portions of this message have been removed]
--
Maybe she awoke to see the roommate's boyfriend swinging from the
chandelier wearing a boar's head.
Something which you, I, and everyone else would call "Tuesday", of course.
