Integration testing transactions and optimistic locking with Spring and JUnit

Posted on by

I did some badness today.

I wanted an integration test to check to see if my @Transactional method actually did rollback on an optimistic lock failure. It’s a pretty business critical method so I wanted to be sure that the whole @Transactional and @Version annotation voodoo actually works.

The approach I took was to inject, what I called a “slowRepository” into the object with the @Transactional method. The slowRepository is just a mockito mock of the object which “answers” (using “thenAnswer”) to the “findBy…” with some custom code.

The idea is that at some point during the @Transactional method the slowRepository is called and the “answer” code is invoked. In the test, the answer code follows along the lines of:

1. Grab the data it requires from the (not slow) repository (the repository the slowRepository is mocking)
2. Switch back the slowRepository for the not slow repository
3. Invoke the @Transactional method again on a separate thread
4. Sleep for a bit
5. Wake up and return the data from step 1

The @Transactional call on the separate thread completes and commits before slowRepository wakes up. When it does, slowRepository returns stale data and the @Transactional method then fails accordingly.

The problem I encountered was using the setters for my @Autowired dependencies on the bean with the @Transactional method. I needed to use the setters so that I could switch in and out the slowRepository, but couldn’t because Spring AOP proxies are implementations of an interface, not subclasses (by default – yes I realise you can get Spring to proxy the target class using CGLIB). I found this blog post which explains how to get at the target object behind a Spring proxy. I converted it to Scala:

…which is pretty ninja.

11,931 thoughts on “Integration testing transactions and optimistic locking with Spring and JUnit”

  4. Your style is unique in comparison to other people I have read stuff
    from. Thank you for posting when you have the opportunity,
    Guess I will just bookmark this web site.

  10. When someone writes an paragraph he/she keeps the
    thought of a user in his/her brain that how a user can understand it.
    So that’s why this piece of writing is amazing. Thanks!

  12. Everything published was very logical. But, think on this, what
    if you were to write a killer headline? I mean, I don’t want to
    tell you how to run your blog, but what if you added something that grabbed people’s attention? I mean Integration testing transactions and optimistic locking
    with Spring and JUnit | freestyle developments is a little boring.
    You should peek at Yahoo’s home page and note how they write news headlines
    to grab viewers interested. You might try adding a video or a picture or two to grab people excited about
    everything’ve written. In my opinion, it could bring your posts a little bit more interesting.

  20. Hello just wanted to give you a quick heads up.
    The words in your content seem to be running off the screen in Chrome.

    I’m not sure if this is a formatting issue or something
    to do with browser compatibility but I thought I’d post to let you know.
    The style and design look great though! Hope you get the issue resolved
    soon. Many thanks

  22. Woah! I’m really digging the template/theme of this blog. It’s simple, yet effective.
    A lot of times it’s hard to get that “perfect balance” between user friendliness and visual appearance.

    I must say you’ve done a excellent job with this.

    Also, the blog loads super fast for me on Opera. Exceptional
    Blog!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>