views:

1180

answers:

4

While developing a Grails 1.0.5 app I'm appaled at how slow the grails test-app command is. Even though the actual tests take just ~10 seconds, the whole execution adds up to

real 1m26.953s user 0m53.955s sys 0m1.860s

This includes grails bootstrapping, loading plugins, compiling all the code etc.

Any hints on how to speed up the grails test-app execution would be greatly appreciated.

+1  A: 

If you're still using Groovy 1.5.x you could probably of shave a few seconds by upgrading to Groovy 1.6

Kimble
Thanks for the answer. I'm not going to make that move since I'm uncertain of how Grails 1.0.x will work with 1.6.x and 1.5.x is the bundled one.
Robert Munteanu
+5  A: 

There aren't any hard and fast rules for speeding it up, and the performance issues that you're seeing might be specific to your app.

If your bootstrapping is taking ~75 seconds, that sounds pretty long. I'd take a close look at whatever you have in your Bootstrap.groovy file to see if that can be slimmed down.

Do you have any extra plugins that you might not need (or that could have a major performance penalty)?

This might not be a possibility for you right now, but the speed improvements in grails 1.1.1/groovy 1.6.3 over grails 1.0.5/groovy 1.5.7 are fairly significant.

Another thing that really helps me when testing, is to specify only integration tests or only unit tests if I'm workiing on one or the other:

grails test-app -unit

grails test-app -integration

You can also specify a particular test class (without the "Tests" prefix), to run a single test which can really help with TDD (ex for "MyServiceTests" integration):

grails test-app -integration MyService

In grails 1.1.1, bootstrapping with 5 plugins and ~40 domain classes takes me less than 20 seconds.

Ted Naleid
Thanks for the suggestions - I'd like to add that this is my slow dev hardware as well. Moving to grails 1.6.3 cut off just 5%.
Robert Munteanu
@Robert You must mean groovy 1.6.3.
Josh Brown
+10  A: 

You can use interactive mode to speed up your test runs.

Just run

grails interactive

Then type

test-app

The first time will be the same as usual but each time after that will be dramatically faster. There are currently some issues with interactive mode (like running out of memory after a few runs) but I still find it worth it.

Brilliant! Thank you.
Robert Munteanu
I just recommend setting your permgen space more generously or you'll run out after a dozen cycles. This is what I use: -XX:PermSize=64m -XX:MaxPermSize=512m
Xymor
We run our grails project via Maven, in this case the first command is: mvn grails:exec -Dcommand="interactive".
David Padbury
Also, after the first run you can rerun the test-app command by just pressing Enter.
David Padbury
+1  A: 

grails now comes with http://grails.org/Testing+Plugin installed. this mocks the domain stuff, so you can do some testing of domain classes as unit tests. they run pretty fast.

Ray Tayek