> I’ve never really subscribed to any of the test-driven-development manifestos or practices that I’ve encountered.
I feel the exact opposite. I've worked in project with a lot of legacy code, both with BDD or with UTs that we added latter on.
Even with the best intentions the latter always failed: we always ended up doing a lot of unreadable tests that had no meaning and that we were afraid to look at. However, when I was working in a team fully committed on BDD, we were looking at the tests before looking at the code, the tests were in the center of the developing process, and we were able to write fast, solid, and simple tests.
Nowadays, I'm more interested on articles that understand that tests can be a pain too. And tbh I don't really trust articles that aim at a high coverage without talking about the different challenges that comes with tests.