Should concrete classes avoid calling other concrete classes, except for data objects?

Posted by Kazark on Programmers See other posts from Programmers or by Kazark
Published on 2012-09-14T17:30:36Z Indexed on 2012/09/14 21:47 UTC
Read the original article Hit count: 220

Filed under:

interfaces

|

abstraction

|

solid

In Appendix A to The Art of Unit Testing, Roy Osherove, speaking about ways to write testable code from the start, says,

An abstract class shouldn't call concrete classes, and concerete classes shouldn't call concrete classes either, unless they're data objects (objects holding data, with no behavior). (259)

The first half of the sentence is simply Dependency Inversion from SOLID. The second half seems rather extreme to me. That means that every time I'm going to write a class that isn't a simple data structure, which is most classes, I should write an interface or abstract class first, right? Is it really worthwhile to go that far in defining abstract classes an interfaces? Can anyone explain why in more detail, or refute it in spite of its benefit for testability?

© Programmers or respective owner

Related posts about interfaces

Should interfaces inherit interfaces

as seen on Programmers - Search for 'Programmers'
Although this is a general question it is also specific to a problem I am currently experiencing. I currently have an interface specified in my solution called public interface IContextProvider { IDataContext { get; set; } IAreaContext { get; set; } } This interface is often used throughout… >>> More
Should interfaces extend (and in doing so inherit methods of) other interfaces

as seen on Programmers - Search for 'Programmers'
Although this is a general question it is also specific to a problem I am currently experiencing. I currently have an interface specified in my solution called public interface IContextProvider { IDataContext { get; set; } IAreaContext { get; set; } } This interface is often used throughout… >>> More
What problems will I face if I remove the concept of interfaces from my code?

as seen on Programmers - Search for 'Programmers'
I have been programming for many years but I am still not comfortable with the concept of "Interfaces". I try to use interfaces but many times I don't see a mandatory use for it. I think this is probably because the projects weren't so big, or because interfaces are more useful when teamwork is involved… >>> More
Explicit C# interface implementation of interfaces that inherit from other interfaces

as seen on Stack Overflow - Search for 'Stack Overflow'
Consider the following three interfaces: interface IBaseInterface { event EventHandler SomeEvent; } interface IInterface1 : IBaseInterface { ... } interface IInterface 2 : IBaseInterface { ... } Now consider the following class that implements both IInterface1 and IInterface 2: class… >>> More
How to force multiple Interfaces to include certain the same properties?

as seen on Stack Overflow - Search for 'Stack Overflow'
I am trying to figure out a way to force all of my Interfaces to include properties of the same name/type. For example: I have two Interfaces; IGetAlarms and IGetDiagnostics. Each of the Interfaces will contain properties that are specific to the Interface itself, however I want to force the two… >>> More

Related posts about abstraction

Is there a way communicate or measure levels of abstraction?

as seen on Programmers - Search for 'Programmers'
I'll be the first to say that this question is a bit... out there. But here are a couple questions I bear in mind : Is abstraction continuous or discrete? Is there a single unit of abstraction? But I'm not sure those questions are truly answerable or even really makes sence. My naive answer would… >>> More
What is the value in hiding the details through abstractions? Isn't there value in transparency?

as seen on Programmers - Search for 'Programmers'
Background I am not a big fan of abstraction. I will admit that one can benefit from adaptability, portability and re-usability of interfaces etc. There is real benefit there, and I don't wish to question that, so let's ignore it. There is the other major "benefit" of abstraction, which is to hide… >>> More
Objective-C: how to prevent abstraction leaks

as seen on Stack Overflow - Search for 'Stack Overflow'
I gather that in Objective-C I must declare instance variables as part of the interface of my class even if these variables are implementation details and have private access. In "subjective" C, I can declare a variable in my .c file and it is not visible outside of that compilation unit. I can declare… >>> More
How much abstraction is too much?

as seen on Stack Overflow - Search for 'Stack Overflow'
In an Object Oriented Program: How much abstraction is too much? How much is just right? I have always been a nuts and bolts kind of guy. I understood the concept behind high levels of encapsulation and abstraction, but always felt instinctively that adding too much would just confuse the program… >>> More
Abstraction is for lame programmers ? [closed]

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi, there's this senior developer in my company who's (in his own opinion) a pretty good C programmer. I happen to be from functional background (ML, to be specific) and so for me composition and abstraction are the two basic elements of programming. But this MrSmartyPants has got some kind of superiority… >>> More