"Only mock types you own" is a "tra...

2010-08-13T07:46:33.066+01:00

"Only mock types you own" is a "training wheels" rule, that helps to break through common misunderstandings about the technique. Sometimes you have to break it.

That said, maybe you should be mocking at a level about the OpenGL layer. Maybe not, but it's probably worth looking at.

Question. I need to verify classes to use OpenGL (...

2010-08-12T15:58:14.530+01:00

Question. I need to verify classes to use OpenGL (C++). It is possible to mock OpenGL using Google Mocks.

Normally, I agree completely - don't mock types you own. However, in order to efficiently automate unit testing for OpenGL related objects, mocking out the relevant parts of the API seems to be the way to do it. This also allows for TDD, even with OpenGL development.

Note that since OpenGL is actually a procedural API, there's no mock object per se; the test code is linked against a mock library which provides GMock implementations of OpenGL. The production code thus uses OpenGL directly; only the tests arrange things to allow for mocking.

Do you folks have any other suggestions or ideas?

Comments on Mock Objects: Only mock types you own (revisited)

"Only mock types you own" is a "tra...

Question. I need to verify classes to use OpenGL (...