October 28, 2010 · 7:00 PM
This location is shown only to members
Programmers, no matter what they tell you, don't test only because they don't know how to do it. Testability needs to be embedded in the code, and cannot be achieved if is not planned for. That is why I try to explain using simple examples how to achieve testable, well-written code, and then how to refactor it, to get rid of duplication and hardly testable code. The talk is built around the four main properties of the unit test, where I explain how to achieve each by applying some of the well and not-so-well known programming techniques.