To Test, or Not To Test…

There are several reasons for writing automated tests, such as ensuring the code works as expected, preventing regressions, and driving the implementation. But tests need effort to be written and maintained. So, whether to write and keep a test or not is a trade-off decision. In this workshop, we’ll discuss the trade-offs and how to affect them towards needing fewer tests while keeping quality at the same level. You’ll see how to combine automated tests with the power of the compiler, type system, and vertical slicing to maximise confidence with as little effort as possible.

Urs Enzler is a software architect and developer specializing in the .NET platform and Azure. Passionate about building products with a rapid and continuous feedback cycle, he embraces agile principles and continuous delivery. In addition to working on the TimeRocket time tracking product, he is a consultant on software architecture and technical aspects of continuous delivery teamwork such as evolvable design, test-driven development, and the like. Beyond his work, Urs co-organizes the .Net Usergroup Zentralschweiz and shares his insights on Planetgeek.