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,484 thoughts on “Integration testing transactions and optimistic locking with Spring and JUnit”

  4. uk poker tour, online casino license in india (Scotty) jack milwaukee and new zealand gambling sites, or best nz casino bonuses

  14. Everything is very open with a precise explanation of
    the challenges. It was definitely informative.
    Your site is useful. Thank you for sharing!

  15. obviously like your website but you need to test the spelling on quite a few of your posts.
    A number of them are rife with spelling issues and I find it very troublesome to inform the truth nevertheless I’ll definitely come again again.

  21. Very quickly this web site will be famous amid all
    blogging visitors, due to it’s good content

  25. Nice post. I was checking continuously this blog and I am impressed!

    Extremely helpful information specifically the last part :
    ) I care for such information much. I was seeking this particular info for a very long
    time. Thank you and best of luck.

  26. Great post. I used to be checking continuously this blog and I
    am inspired! Very helpful information particularly the ultimate phase :
    ) I take care of such information much. I used to be looking for this particular info
    for a very long time. Thanks and best of luck.

  27. Ι’m reaⅼly enjoying tһｅ theme/design of youг blog.
    Do үou ever run into any internet browser compatibility problems?
    A few of my Ьlog readеrs hνe comрlained about my site not operating
    correctly in Explorer but looks great in Chrome. Do you haνe any tips to helop fix this issue?

  30. When someone writes an piece of writing he/she keeps the thought
    of a user in his/her mind that how a user can know it. Thus that’s why this post is outstdanding.
    Thanks!

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>