Clever Geek Handbook

Lots of spock tests results in very long compile times in eclipse

We have a lot of tests in 600 groovy files that use Spock. All test classes extend from AbstractSpecification.groovy, which has many Service-Classes introduced and many helper methods for using those classes (Spring, Autowired).

We are using Eclipse and every change to the Abstract class results in a recompilation (Building workspace, Invoking Maven Project Builder). But during development, this recompilation got slower and slower. Now with 600 tests, we have to wait for aprox. 14 minutes before the end of the eclipse, which makes the test project almost unusable.

I think there is nothing out of the ordinary with a lot of tests with an abstract class, so I wonder if people have encountered the same problem with Spock. I changed the groovy Version, Plugin Version, but nothing helped. Only a decrease in the number of test classes.

Any ideas? Thanks in advance!

Datasheet: - Eclipse Kepler SR2, Groovy -Eclipse + Compiler Plugin 2.9.1, groovy 2.0.7, Spock Version 0.7- groovy -2.0

+3


source to share


1 answer


As a result, we translated all Groovy tests to Java. With a lot of tests, profiling, etc. This was the only solution we found. This leaves a bitter taste, because Groovy has many benefits, but it caused us a lot of problems.



0


source






More articles:


All Articles