In this post I will show you quickly how handy JUnit rules are if you need to solve the following challenge A method catches an exception and has to perform some extra tasks before rethrowing or throwing a wrapper exception. Calls to the extra tasks and the thrown exception should be verified by a unit test. This means you have some […]
Category Archives: Testing
Arquillian – Very first best practice
During usage of Arquillian I figured out some things that could be a starting point for best practices when testing with Arquillian. In my application I had some defaults that I have to do every time, when I would like to implement a new test. Add logging Add persistence.xml For different domains, add all classes […]
Started JEE – Testing with Arquillian
Some time ago I came to the point where I need to do integration tests for my JEE applications at work. In Spring this is fairly easy, just use the SpringJUnitRunner and most of the work is done by Spring. Possibly you have to choose the right profile or do some minor configuration setup. But […]