Comments on: To Mock Or Not To Mock http://www.blizzo.com/to-mock-or-not-to-mock/ Randomness for you since 1976 Wed, 07 Jan 2009 03:37:39 +0000 http://wordpress.org/?v=2.6.2 By: Peter Williams http://www.blizzo.com/to-mock-or-not-to-mock/#comment-238 Peter Williams Fri, 15 Jun 2007 17:37:33 +0000 http://www.blizzo.com/?p=58#comment-238 <strong>Mocking...</strong> Mr Whitney recently posted an article in which he described mock objects as “bug aggregators”. I once held a similar point of view. Back then my belief was that test doubles (mock, stub, etc) should only be used when real objects would not ... Mocking…

Mr Whitney recently posted an article in which he described mock objects as “bug aggregators”.
I once held a similar point of view.
Back then my belief was that test doubles (mock, stub, etc)
should only be used when real
objects would not …

]]> By: Catherine http://www.blizzo.com/to-mock-or-not-to-mock/#comment-239 Catherine Tue, 12 Jun 2007 05:23:20 +0000 http://www.blizzo.com/?p=58#comment-239 hallelujah on separating hibernate from the database I had worked very happily not knowing this beast. Once I met it, I can't say we're friends. But then again, I think people - namely your friendly database architect - should control the schema, not what make hibernate the happiest. Not that that was Morgan's point at all, I at least know that much. hallelujah on separating hibernate from the database

I had worked very happily not knowing this beast. Once I met it, I can’t say we’re friends. But then again, I think people - namely your friendly database architect - should control the schema, not what make hibernate the happiest.

Not that that was Morgan’s point at all, I at least know that much.

]]> By: Jason E. Rist http://www.blizzo.com/to-mock-or-not-to-mock/#comment-240 Jason E. Rist Thu, 07 Jun 2007 17:35:48 +0000 http://www.blizzo.com/?p=58#comment-240 I've encountered this recently at work as well. From my experience Mocks do have their place, but they seem to be in what you mentioned - simulating lookup data from a database. Until we get a chance to rewrite our code to use HSQL and then separate Hibernate from the database, we have to use Mocks for our DAOs. (Side-notes: we're writing the tests for code that is already in place and haven't yet gotten to the Mocks for the DAOs. I'm sure it will be painful soon!) I’ve encountered this recently at work as well. From my experience Mocks do have their place, but they seem to be in what you mentioned - simulating lookup data from a database. Until we get a chance to rewrite our code to use HSQL and then separate Hibernate from the database, we have to use Mocks for our DAOs. (Side-notes: we’re writing the tests for code that is already in place and haven’t yet gotten to the Mocks for the DAOs. I’m sure it will be painful soon!)

]]>