Everyone has heard of the test automation pyramid - you should have lots of unit test automation, and less user interface tests at the top. But a lot of places are still struggling with this. Typically in reality we have more UI tests than unit ones - the "ice cream cone" reality.In this session we'll examine a couple of scenarios, and work to build a better unit test framework. We'll take code which has unit testing in it which isn't that great, and apply some principles to make it better.

The key take homes will be:
* Unit testing is fast
* Everything starts with the design - we'll look at how the code is written can aid or hamper testing
* Unit testing ideally should be simple, not elaborate, ideally testing only one thing per test.