Besides other cool features, Spring 2.5 brought completely rewritten support for functional tests. Before this version, Spring had support for functional tests using JUnit 3 only. If you needed to use JUnit 4 or TestNG you just did not get any help from the framework
Now you can use brand new annotations and you are not constrained in your choice of testing framework any more. For complete information, please consult Spring reference, I will show only small subset of the new features. Let’s take a look on the first example.
Here we see normal class with some annotations. But it is not normal class, it is JUnit 4 test. By
RunWith annotation we are extending usual JUnit test runner in order to enable Spring support. Then we have to define where application context XML file(s) are (
@ContextConfiguration annotation). Now we can use
Autowire annotations to have all necessary dependencies injected. If we use annotation
Transactional we obtain similar behavior as when we were using old
AbstractTransactionalSpringContextTests. It means:
The application context is shared for all test methods (in all test classes). So all the stuff is initialized only once. If your test does some changes to the application context and it has to be therefore discarded, you can use
All test methods are run in transaction which is rolled back at the end of every test method. You can change this behavior by
Rollbackannotation or by
The new Spring test support is great. I just miss one thing. Old test support classes gave me possibility to finish and start a transaction in the middle of the test method (by calling
startNewTransaction). I agree, that you do not need such feature very often, but sometimes it is handy. I was not able to find something similar in the new support classes. Finally I found a solution but it is not so straightforward as the old one (If you know better one please inform me).
In the following example I am trying to test whether my DAO is fetching addresses of the client so I do not get LazyInit exception. In my test I need to store a client to the database, finish the transaction, then load the client from the DB in a new transaction and finally check if the addresses are accessible even when no transaction is active.
As you can see, I have marked the method as
NonTransactional. Therefore, Spring does not create a transaction for me and I can manage my transaction programmatically. For example using Spring transaction template. And that’s it.
The source code can be downloaded from SVN repository here.
Note: If you wonder why the hell I have started to write in something that looks almost like English when apparently I do even more mistakes than in Czech, the answer is simple. I just need to practice my English (apart from that I want to be world famous, not just known in Czech Republic)
This is one of the coolest feature of the 2.5 release. I really appreciate the annotation approach that dramatically reduces amount of a “glue” code. There is also simplified way for extensions of the test execution behavior, for details see a chapter “126.96.36.199. Key abstractions” in the documentation.
Excellent article, very useful indeed, thanks!
How do you get a reference to transactionManager? Do you @Autowire it into your Test class?
Yes, it is autowired full source code is here
info about TransactionTemplate really useful )