Any experience with groovy as your primary testing language?

I think I'm not the only one who will ask this question next time. After some experience with RoR, I am impressed with the power of dynamic languages. However, many projects have to use the Java stack differently. Since testing is an important part of any project, I would like to hear your experience in creating a corporate project with groovy as the main testing language and NOT in production code. He believes this is an ideal scenario to start with this language. How is your experience for this constellation, especially regarding the following points:

  • Integration in Eclipse: calling java apis, possibly with automatic full functions?
  • Stability of any groovy performance if you have a typical java stack (Spring, OR-Mapper)
  • Groovy test integration on build server and continuous ant integration
  • Adaptability by java team of 4 developers

Thanks a lot!

Denis.

+3
source share
2 answers
  • Integration in Eclipse: minimal, but enhanced by SpringSource , with expected good results in a couple of months;
  • Groovy is stable in my opinion, but performance is not stellar. But again, unit testing does not have to be fast, fast;
  • Integration: this is done for maven and ant;
+2
source

Eclipse . , . , , .

. JVM, Groovy. , , Java, Java-, . , , . Groovy .

. Groovy Java. Groovy , JUnit Groovy. Groovy , Java. CruiseControl Maven.

Groovy . Java, 4 , , , Java, , .

+1

Source: https://habr.com/ru/post/1710064/


All Articles