Have you ever cried out: what the hell does method/class/module do?! Then this talk is for you. It turns out, not all code is self explanatory. Oftentimes, you’ll need more than the code itself to get a good grasp on it – you need functional documentation.

Now, nobody likes writing documentation – and for good reason! Writing and maintaining traditional docs takes up a lot of time and energy while offering little added benefit. So no, you shouldn’t write extensive specification documents – you should write better tests. By paying some extra attention to their scope and readability, you can transform your tests from a simple validation mechanism to an authoritative source of information for developers.

At the end of this session, you’ll know how to write readable tests that greatly improve the development speed of you and your team by codifying your application’s specs. This talk is for all developers who have been burned too many times by incorrect or altogether missing documentation.

As an added benefit, you’ll learn how to write tests that only break when requirements change, facilitating continuous refactoring.