Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Thanks for the reply. So if I understand correctly, you are saying that I started from the "smaller" classes that are composing the Game, instead of starting from the Game itself. I agree, I did that because I was stuck with this Run() problem. The other thing you are suggesting is basically use an external logic passed through the game (that can be mocked) to see if the game behaves in a certain way based on what is set on that logic. Is that correct? Commented Jul 22, 2019 at 12:53
  • 2
    This is a good answer - and can also be applied to working with engines like Unity - where your MonoBehaviour would be a mini I/O wrapper (events in, behaviour out) around logic for a particular game component. The key lies in making those wrappers as thin as possible so they deal only with the "impure" outside world and map cleanly to a "pure" test-driven model. After that it's just plain old TDD. Commented Jul 22, 2019 at 12:59
  • Just a small nitpick - Mocks are scary (because they test much more implementation than behaviour and as such are brittle), but one should not be dissuaded from using more simple kinds of Test Doubles, mainly Stubs (as those two are often misunderstood as being two names for the same thing). Commented Jul 22, 2019 at 13:14