Executing Groovy (Grails) tests is slow

I'm using IntelliJ 13, and when I try to run a test on my MacBook, there's a whole lot of action going on (loading groovy sources, canonicalization, semantic analysis, etc) when running a test. The whole process on my MacBook takes 10 seconds.

However, when nothing has changed, and I try to rerun the tests again, the who process is taking place again. Nothing is cached, or anything like that, it takes another full 10 (14 in this case) seconds for a single Unit test to run. I'd consider that extremely slow. I'm talking about unit tests here, not about integration tests (which I 'expect' to be slow). The test itself is doing nothing, just this: assertTrue(true).

It would be nice if this could be improved a bit, and maybe some parts could be skipped if running a test the second time.

---

*Imported from [IDEA-115860](https://youtrack.jetbrains.com/issue/IDEA-115860) · Type: Performance Problem · Votes: 1*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*

Start by reproducing the report in IntelliJ 13 on a MacBook with a minimal Groovy/Grails unit test such as assertTrue(true), then compare first and unchanged reruns. Trace the plugin's test execution and Groovy source-processing path, including loading, canonicalization, and semantic analysis. Done means repeated unit-test runs avoid unnecessary work and are materially faster without changing test results.

Written by the indexing model from the issue text.