Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • "as long as your tests do not assume the use of advanced groovy features" I think the problem is that the Spock framework uses those advanced features to inject mock classes into other classes, thus requiring some classes to be compiled using the groovy compiler. Which is what my concern really is: We're testing the Groovy version of our code, not our original Java code. I personally would like to just export a single jar to the testing project, but I've been told that won't work here (Groovy, advanced features, injecting mock objects that span many layers, etc)... so should I be concerned? Commented Feb 27, 2013 at 15:02
  • I have not really read up on Spock much, but I see no reason why your application code would need to be compiled with Groovy instead of Java compiler. The tests themselves would be compiled with groovy, and the mock objects would be groovy classes, since there is no problem injecting these groovy classes into the Java application for testing. Commented Feb 27, 2013 at 15:12
  • Maybe you could ask the developers of Spock this question? Also, ask your dev team (or whomever suggested Spock) to create a simplified mock project with similar dependencies and functionality to your current project. Let them write the tests using Spock (if they have the time to waste). You should be able to make a better determination of risk versus development time saved and decreased code complexity from this POC. I always find a POC over the problem domain to be more enlightening than a plain old demo... Commented Feb 27, 2013 at 15:17
  • 1
    Looking at this example, it is quite clear that testing a stack can be done, and there is no reason why the stack cannot be a simple java compiled class, as long as the class is in groovy's class path when executing the tests. Commented Feb 27, 2013 at 15:21