Over a million developers have joined DZone.

Yet More Spock Magic: Mocks

DZone's Guide to

Yet More Spock Magic: Mocks

· Java Zone
Free Resource

The single app analytics solutions to take your web and mobile apps to the next level.  Try today!  Brought to you in partnership with CA Technologies

Spock's built-in mock object capabilities are just a dream to use ... unlike other systems I've used, it doesn't get in your way, or force you to think backwards or inside out. Once again, some listings. These are for tests of Tapestry IoC's AspectDecorator service, which is used to create a wrapper interceptor around some other object. The test below shows how a supplied MethodAdvice callback object is invoked by the interceptor, if the advice is associated with the invoked method.

TestNG with EasyMock (Java)

public class AspectInterceptorBuilderImplTest extends IOCInternalTestCase
    private AspectDecorator decorator;

    public void setup()
        decorator = getService(AspectDecorator.class);

    public interface Subject
        void advised();

        void notAdvised();

    public void some_methods_not_intercepted() throws Exception
        Subject delegate = newMock(Subject.class)

        MethodAdvice advice = new MethodAdvice()
            public void advise(MethodInvocation invocation)
                assertEquals(invocation.getMethod().getName(), "advised");




        AspectInterceptorBuilder<Subject> builder = decorator.createBuilder(Subject.class, delegate, "<Subject>");

        builder.adviseMethod(Subject.class.getMethod("advised"), advice);

        Subject interceptor = builder.build();



Even this example is a bit streamlined, as some of the mock object capabilities, such as methods newMock(), replay() and verify() are being derived from the TestBase base class.


interface InterceptorSubject {

  void advised()

  void notAdvised()

class AspectInterceptorBuilderImplSpec extends AbstractSharedRegistrySpecification {

  private AspectDecorator decorator

  def setupSpec() {
    decorator = getService AspectDecorator

  def "ensure that non-advised methods are not passed through the MethodAdvice object"() {
    InterceptorSubject delegate = Mock()
    MethodAdvice advice = Mock()

    def builder = decorator.createBuilder(InterceptorSubject, delegate, "<InterceptorSubject>")

    builder.adviseMethod(InterceptorSubject.getMethod("advised"), advice)

    InterceptorSubject interceptor = builder.build()




    1 * advice.advise(_) >> { MethodInvocation mi ->
      assert mi.method.name == "advised"
    1 * delegate.advised()
    0 * _




    1 * delegate.notAdvised()
    0 * _


Spock's wonderful when: / then: blocks organize the behavior into a stimulus followed by a response; using EasyMock, you have to train the mock objects for the response before introducing the stimulus (the method invocation). Further, with EasyMock there's one API for methods that return a fixed response, a second API for methods that throw an exception, and a third API for methods where the result must be calculated; in Spock the value after the >> operator is either a literal value, or a closure that can do what it likes, such as the one attached to MethodAdvice.advice() that checks for the expected method name, and then proceed()s to the delegate mock object's method.

I think that a reasonable developer, even without a thorough understanding of Spock, would get the gist of what this test does (perhaps with a little side note about the interaction system inside the then: block). On the other hand, I've seen when training people with TestNG and EasyMock that it very rarely sinks in immediately, if at all.





CA App Experience Analytics, a whole new level of visibility. Learn more. Brought to you in partnership with CA Technologies.


Published at DZone with permission of Howard Lewis Ship, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}