Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

1
  • 1
    Though I think this is a good post, I disagree about what the linked article says about the "hybrid" test. Having "small" integration tests (additionally, not alternatively to pure unit tests, of course) can IMHO be very helpful, even if they cannot tell you exactly which method contains the wrong code. If those tests are maintainable depends on how clean the code for those tests is written, they are not "dirty" per se. And I think the goal of those tests can be very clear (as in the example of the OP). Commented Jan 23, 2013 at 12:16