The slides used for this session are available to download from here.
If there is one time when we find it easy to take shortcuts, it's when writing tests. Whether we're under the cosh or have an overly-optimistic view of our ability to write self-documenting code, instead of creating tests that support the production code and development process we can find ourselves producing WTFs (Weak Test Functions). The net effect is often a viscous cycle that disparages, instead of encourages us.
In the past I've tried many different ways to try and short-circuit the test writing process, but have only come up short every time. This session takes a look at why skimping on elements of the test structure, such as organisation, naming and scope only leads to pain and hardship in the long run. Along the way we'll uncover the truth behind common folklore, such as only having one assertion per test.
Chris is a freelance programmer who started out as a bedroom coder in the 80s, writing assembler on 8-bit micros; these days it's enterprise grade technology in plush corporate offices. He also commentates on the Godmanchester duck race.
To see this fantastic session and others like it, buy your ticket now.buy tickets