I can mock calls to:
MyDomainClass.createCriteria().list{
eq(\'id\',id)
eq(\'anotherParameter\',anotherParameterId)
}
with:
<
I wouldn't bother. Instead create methods in your domain class and mock those. This makes testing easier but more importantly has the advantage of keeping persistence where it belongs instead of scattering it throughout the code base:
class MyDomainClass {
String foo
int bar
static MyDomainClass findAllByIdAndAnotherParameter(long id, long anotherParameterId) {
createCriteria().list {
eq('id',id)
eq('anotherParameter',anotherParameterId)
}
}
static MyDomainClass getByIdAndAnotherParameter(long id, long anotherParameterId) {
createCriteria().get {
eq('id',id)
eq('anotherParameter',anotherParameterId)
}
}
}
Then in your tests, just mock it as
def testInstances = [...]
MyDomainClass.metaClass.static.findAllByIdAndAnotherParameter = { long id, long id2 ->
return testInstances
}
and
def testInstance = new MyDomainClass(...)
MyDomainClass.metaClass.static.getByIdAndAnotherParameter = { long id, long id2 ->
return testInstance
}
I've found a solution that doesn't compromise my ability to write unit tests -
def myCriteria = new Expando();
myCriteria .get = {Closure cls -> returnThisObject}
MyDomainClass.metaClass.static.createCriteria = {myCriteria }
which does exactly what I wanted and potentially supports testing supplied arguments. Thanks for the other response. Hope this is useful to others testing domain/createCriteria() methods.
This should be much simpler now with the GrailsUnitTestCase.mockDomain
1 method.
package sandbox.grails.foo
class Something {
String name
}
package sandbox.grails.foo
import grails.test.mixin.*
import org.junit.*
@TestFor(Something)
class SomethingTests {
void testSomething() {
mockDomain(Something, [
new Something(name: 'Foo'),
new Something(name: 'Bar'),
new Something(name: 'Boo'),
new Something(name: 'Baz')
])
def actuals = Something.createCriteria().list(sort: 'name', order: 'asc') {
like('name', '%oo')
}
assertEquals 2, actuals.size()
}
}