• Stubs vs Mocks - In this article, I’d like to discuss the differences in using stubs and mocks and show how you can abandon using mocks even in the cases where you need to verify that objects interact with each other correctly. Test-induced design damage or why TDD is so painful How to do painless TDD Integration testing or how to sleep well at nights The most important TDD rule Stubs vs Mocks TDD best practices [Enterprise Craftsmanship]

Permalink | From 27 July 2015 to 02 August 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

• The most important TDD rule - In the previous articles, we discussed what causes the pain while writing unit tests (mocks), and how to make TDD painless (get rid of the mocks). Today, I want to set the groundwork and discuss why mocks actually cause so much pain to us, developers. Test-induced design damage or why TDD is so painful How to do painless TDD Integration testing or how to sleep well at nights The most important TDD rule Stubs vs Mocks TDD best practices [Enterprise Craftsmanship]

Permalink | From 20 July 2015 to 26 July 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

• Integration testing or how to sleep well at nights - Unit testing is good at checking the correctness of your code in isolation, but it’s not a panacea. Only integration tests can give us confidence that the application we develop actually works as a whole. They are also a good substitute for mocks in the cases where you can’t test important business logic without involving external dependencies. Test-induced design damage or why TDD is so painful How to do painless TDD Integration testing or how to sleep well at nights The most important TDD rule Stubs vs Mocks TDD best practices [Enterprise Craftsmanship]

Permalink | From 13 July 2015 to 19 July 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT

• How to do painless TDD - Last week, we nailed the root cause of the problems, related to so-called test-induced damage - damage we have to bring into our design in order to make the code testable. Today, we’ll look at how we can mitigate that damage, or, in other words, do painless TDD. Test-induced design damage or why TDD is so painful How to do painless TDD Integration testing or how to sleep well at nights The most important TDD rule Stubs vs Mocks TDD best practices [Enterprise Craftsmanship]

Permalink | From 06 July 2015 to 12 July 2015 | Last updated on: Mon, 7 Jun 2021 09:11:15 GMT