Is it necessary to remove the metaClass after using mockDomain in Grails unit tests?

Question

mockDomain provides dynamic methods like save(), validate(), ... for a domain class.

Is it necessary to remove the meta classes for each class I mock using mockDomain?

class UserTests extends GrailsUnitTestCase {

    protected void setUp()
    {
        super.setUp()
        mockDomain User
        mockDomain Address
    }

    protected void tearDown()
    {
        super.tearDown()
        def remove = GroovySystem.metaClassRegistry.&removeMetaClass
        remove User
        remove Address
    }

}

Nathan Hughes · Accepted Answer · 2012-03-30T17:25:04.250

3

You don't need to do that. The mockDomain method calls registerMetaClass, which stashes away the current metaClass and substitutes a new one, so that on tearDown the test can restore the old metaClass for you. When you do need to add methods to a metaClass yourself, you can call registerMetaClass (before you add your changes, of course) and once it's done the test will do the cleaning up.

edited Mar 30 '12 at 17:25

answered Mar 30 '12 at 12:10

Nathan Hughes

94,330
19
181
276

score 0 · Answer 2 · answered Mar 30 '12 at 11:59

0

Nope. Out of curiosity, what would lead you to believe that you would need to do that?

answered Mar 30 '12 at 11:59

Gregg

34,973
19
109
214

A discussion with a workmate. I was right and it's not necessary – Arturo Herrero Mar 30 '12 at 12:32
I was right too, but I guess the other guys answer was better for you? – Gregg Mar 30 '12 at 13:35
@Gregg: yes, you're right, and you were first. but answers with an explanation usually do better. – Nathan Hughes Mar 30 '12 at 13:44

Is it necessary to remove the metaClass after using mockDomain in Grails unit tests?

2 Answers2