One Mock Too Far

Tests should save our money and time. How is it that they often become the stumbling block and slow down the work? They fail every time you try to do some refactoring and are difficult to maintain ultimately increasing the cost of software maintenance.

If you have such problems it means that you may have gone a “one mock too far ” – testing the wrong things, and you using mock in the wrong places. During my talk I will give examples how to test different types of code wisely so tests will protect your application and will not be a burden for you.

Video producer: