Automated TDD Principles #2 – Strong Harnesses

In the previous article I made the case for Automated Testing. Today we will talk about the tools.

  • What qualities does a strong testing framework have?
  • What guidelines should developers use when choosing one?
  • Why do those guidelines matter?
  • What tools would I recommend?

I will use the terms Harness, Framework and Library interchangeably. Be warned.

All of this and more, after a few choice bold words, a digit, a hash, and a hyphen. Continue reading “Automated TDD Principles #2 – Strong Harnesses”

Automated TDD Principles #1 – Write Automated Tests

One of the Devs I used to work with has been asking a lot of questions recently, all revolving around what can only be considered the principles I hold dear as a TDD champion. I don’t claim to be a guru, but I hope to be able to start some conversation about the importance of automated testing, some of the principles I hold dear and most of all I intend to engage you readers so I can learn from your experiences and possibly guide you if questions arise.

Let’s dive in.

Continue reading “Automated TDD Principles #1 – Write Automated Tests”

The operation completed successfully.

If Unreal 4 reports back with the following error, don’t freak out.

LogWindows:Error: Windows GetLastError: The operation completed successfully. (0)

This means that you have likely copied or refactored some code, resulting in duplicated code. This does not mean that you screwed up, it could have just been Perforce or Git screwing with you. Do a quick sanity check and make sure that you have your code laid out appropriately and you should be cooking with gas.