Frank Carver's musings about software and life
In almost all areas of software development, and especially in test-Driven Development (TDD), testing is vital. In many ways, automated testing by developers is even more valuable. However, as Jay Fields points out, attitudes to, and practices of, testing vary greatly.
I have found Test-Driven Development (TDD) a surprisingly powerful software development technique over the years, and I’m always interested in reading attempts at explaining why this might be. Here’s another take, this time from Steve Freeman.
Test-Driven Development. A Cognitive Justification?
There’s a continuing discussion about this topic. Rather than create a new post, I thought I’d see how updating this post with a new link would play. Will anyone notice?
Jay Fields recommends using stubs far more often than mocks, a view which aligns pretty well with my own thoughts. I still find most tests using traditional Mock frameworks to be inexpressive, unwieldy and fragile.
Somewhat of a rant against traditional, and often big budget, record/replay acceptance testing tools.