atom feed20 messages in org.codehaus.grails.userRe: [grails-user] which spock plugin ...
FromSent OnAttachments
Roshan DawraniDec 19, 2011 2:05 am 
Roshan DawraniDec 19, 2011 2:24 am 
ld...@ldaley.comDec 19, 2011 2:46 am 
Roshan DawraniDec 19, 2011 2:52 am 
ld...@ldaley.comDec 19, 2011 2:55 am 
Sam CarrDec 19, 2011 3:00 am 
Roshan DawraniDec 19, 2011 3:10 am 
Roshan DawraniDec 19, 2011 3:13 am 
Roshan DawraniDec 19, 2011 3:35 am 
Roshan DawraniDec 19, 2011 4:32 am 
Roshan DawraniDec 19, 2011 4:47 am 
Roshan DawraniDec 19, 2011 5:03 am 
Roshan DawraniDec 19, 2011 5:12 am 
Roshan DawraniDec 19, 2011 5:50 am 
Roshan DawraniDec 19, 2011 7:24 am 
Roshan DawraniDec 19, 2011 7:38 am 
Roshan DawraniDec 19, 2011 8:32 am.zip
ld...@ldaley.comDec 20, 2011 9:06 am 
Roshan DawraniDec 21, 2011 11:33 am 
Luke DaleyDec 21, 2011 11:46 am 
Subject:Re: [grails-user] which spock plugin to use with Grails 2.0?
From:Roshan Dawrani (rosh@gmail.com)
Date:Dec 19, 2011 5:50:36 am
List:org.codehaus.grails.user

Filed: http://jira.grails.org/browse/GRAILS-8516

Cheers.

I wonder is that's what org.codehaus.groovy.grails.test.compiler.GrailsTestCompiler.makeCompileUnit() is doing - effectively adding @TestFor to all the test classes and forcing an implicit visit by TestForTransformation on all of them.

Regardless of how TestForTransformation is coming into the picture, the consistency between the following two is still a bug between Grails 2.0 and Spock's Grails plugin:

DomainClassUnitTestMixin:

grails.plugin.spock.UnitSpec:

On Mon, Dec 19, 2011 at 6:25 PM, Luke Daley <lda@gmail.com> wrote:

Is DomainClassUnitTestMixin being applied implicitly?

I have not started using Grails 2.0 new test support (no usage of @TestFor in my app yet, but TestForTransformation is still kicking in and weaving in these mixin classes, like DomainClassUnitTestMixin).

If that's what you mean, then yes, it is being applied implicitly.