I use the phrase in the title usually to refer to using mock objects in a useless way (mocking ADO.Net or Active Directory or calls to any API that you don't understand). When you're choosing whether to write a small integration test or a mocked test, just think what would give you the actual...

I'm not a particularly good tennis player. Mostly from not having played in years, but even then, I suffered because I can't hit a decent backhand to save my life. I have a big serve and a decent control with my forehand, but all you've got to do to beat me is put the ball where I have to...

Roy has a post up today about TypeMock, testability, and DI . The age old (ok, it just seems like we've been arguing over this for decades) question comes up again "is TypeMock too powerful?" First, let's go pro-TypeMock because the attraction of TypeMock is pretty easy to understand...

Hello, my name is Jeremy, and I sometimes write unit tests specifications that are uglier than sin. Specifically, when I started to look back at the interaction style tests I've been writing over the past couple years I'm finding a bunch of unit tests that are indecipherable to me, the author...

I found an interesting link today from Mario Gleichmann called Test Driven Development and Design By Contract - friend or foe?. I've always been lukewarm toward Design by Contract (DbC). Occasionally I'll run into claims from DbC enthusiasts that using DbC completely eliminates the need or desire...

I've had a couple conversations the past couple weeks about extending test coverage in the user interface and the necessity of writing integrated tests. One person wished his team were doing more automated testing through the UI (web app), and the other person just assumed that testing the UI (WinForms...

Behavior Driven Development (BDD) has been a pretty big topic in some of the email groups I lurk in. I'm seeing BDD cast as a whole new paradigm of development, where as I see BDD as an evolution of TDD with a better syntax and mechanics for expressing the desired functionality with tests/specifications...

The title is a mouthful and accurately implies an alarmingly high jargon to code ration, but I just didn't see anyway to write this post without straying into all of these different subjects. When you try to write an explanatory article you have to walk a tightrope between a sample problem that's...

EDIT: What I should really say is that it isnt' just Designing for Testability, it's Designing with Testability From a question on my Passive View blog post : "should we design for testability, or should we try and test what's designed (perhaps designed badly, so we refactor later)?"...

I've long, long since left the rails of "Build your own CAB" topics and wandered off into "just things you do" when you're building a WinForms application. I'm doing this topic now because it felt easy to do in the midst of a hectic week before some time off. Other topics...