GDC 2014

GDC 2014 Session Scheduler

View, browse, and sort the ever-growing list of GDC sessions by pass type, track, summit, format, and day. With GDC Session Scheduler you can build your schedule in advance, and access it during the show via export or with the GDC mobile app, Please note that adding sessions to your schedule does not guarantee you a seat in that session. Sessions do fill up, so please arrive early to sessions that you would like to attend.

Start building your GDC agenda — create your linked account for the GDC Session Scheduler and the GDC Mobile App now!

Register now for GDC 2014!

Please note: Registration accounts are separate from Session Scheduler. Even if you've registered, please create a Session Scheduler account below.

Export Schedule:

Practical Unit Tests

Andrew Fray  |  Engineer, Spry Fox

Location: Room 304, South Hall

Format: Session
Track: Programming
Vault Recording: Video

Unit testing is common in the wider software world, but it has not taken off in the video game industry. There are many who claim it can't be successfully applied to games. Andrew Fray disagrees, and yet he could not call his first attempt at unit-tested code, a subsystem of a AAA console game, entirely successful. In this talk, Andrew will explain why he believes unit tests are perfectly usable in game development, but that like any technique, they need careful practice and considered application. By dissecting tests from his first project, he will explain the ways in which poor unit tests can affect a project's ability to iterate and grow, while also showing how to avoid these problems in your own code.


Attendees will understand how unit testing can be successfully applied to video game development, and the benefits and drawbacks of this technique. They will see real-life examples of common unit test anti-patterns, understand the problems caused by these anti-patterns, and how to avoid them.

Intended Audience

Programmers who are interested in unit testing or have attempted unit testing (either test-first or test-after), have not had success with it, and want to understand the common pitfalls to avoid.