DEV Community

Discussion on: Why Java interfaces aren't terrible (just strict)

 
bertilmuth profile image
Bertil Muth

Well, for me, a unit isn’t always equal to a class. In other words: I test several classes together. I know people have strong opinions about isolation- for me, it works just fine, and there are several TDD practioners who advocate this style (among them Martin Fowler and Kent Beck, if I‘m not mistaken).

Thread Thread
 
bertilmuth profile image
Bertil Muth

You get fewer tests, that don’t break easily when the implementation changes. The downside is errors are a bit more difficult to find.

Thread Thread
 
simonhaisz profile image
simonhaisz

That's a fair approach. I'm certainly not dogmatic about this stuff; as long as you have a good understanding of the pros and cons involved and accept them, like you do here, that's fine. I do think this takes a bit more discipline around understanding what the "unit under test" is, so adoption could be an issue depending your team.

I don't recall reading anything by Fowler on this specific subject and I ❤️ that man. You wouldn't happen to know the book/blog/talk off hand would you? Sometimes searching for these things can prove to be difficult.

Thread Thread
 
bertilmuth profile image
Bertil Muth

I found a pretty lengthy explanation of Robert Martin, a.k.a. Uncle Bob, who also prefers to test several classes at once if necessary: blog.cleancoder.com/uncle-bob/2017...

Thread Thread
 
simonhaisz profile image
simonhaisz

Thanks for the Sunday reading!

Thread Thread
 
bertilmuth profile image
Bertil Muth

There’s more :) Here’s the interview of Martin Fowler, Kent Beck and DHH about DHHs article “TDD is dead” where they mention that they don’t mock that much. martinfowler.com/articles/is-tdd-d...