Software Craftsmanship Series
The practices that keep code changeable: TDD, refactoring, clean design, and the habits around them.
7 parts
- 1
The Art of Testing: Where Design Meets Quality
From a software developer's point of view
Why you should consider testing as part of your daily development habit and how it's directly linked to the software quality.
- 2
To Mock or Not to Mock
How to escape the mocking hell
Mocking is useful, but 'what to mock' usually turns out to be a more complicated than expected if you don't treat this carefully.
- 3
Test-Driven (Development)
What is challenging about it?
TDD is a design practice, not just a testing technique. Writing tests first changes how you think about code and shape its structure.
- 4
TDD vs BDD
Design or Workflow?
These are two different techniques. The key to each of them is about the mindset and context of what you want to achieve.
- 5
London vs Chicago
It's an integration, not a choice
There are two known schools in TDD: the mockist school (aka Outside-in) and the classicist school (aka Inside-out).
- 6
How to Test Private Methods?
Testing private methods. When and how?
From time to time I have had to face this question: how to test private methods? I have put together in an article the techniques that I usually use.
- 7
Effective Pair Programming
Embracing quality practices in your engineering culture
A practical guide to pair programming that works: roles, rotation, when to pair, common pitfalls, and how to make sessions productive.