Testing Objects

I have never specifically tested object oriented software from the perspective of it being OO software.

I have several books on this topic:

Testing Object-Oriented Systems: Models, Patterns, and Tools

A Practical Guide to Testing Object-Oriented Software

I don't often see this discussed at testing conferences or frequently in articles so I'm not sure it is mainstream.

I think the books make a good case for the testing they discuss, but on the face of it, OO testing looks complicated and requires a coding background to understand it quicker. This is probably why it hasn't made it into common practice as SDET style testers are still rare in the industry overall.

By not doing this type of testing what coverage are you missing? I haven't found many bugs in the OO software I've tested related to OO structure issues, other than complicated OO code it turned out the developer didn't fully understand.

This could be another reason we haven't been forced to deal with this perspective. Maybe there still isn't a lot of good OO code out there that would require it. Our system tests catch the issues, and OO specific techniques aren't generally required.

I need to study the issue more, so I don't have as many answers as I would like. Seeing the books on my shelf recently reminded me to take another look and consider this perspective.