This was originally reported some time back, as a ticket within the GSPOCK project (GPSPOCK-14); however it was suggested to be reported to Grails core.
The attached project shows how using MockFor within tests - in this case Spock using @TestFor - appears to bleed that mock instance into a subsequent test that is trying to use the actual type unmocked.
|Fix Version/s||2.0.4 [ 13099 ]|
|Priority||Major [ 3 ]||Critical [ 2 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Graeme Rocher [ graemerocher ]|
|Resolution||Won't Fix [ 2 ]|