If you are using Mockito, it is sometimes useful to check the parameter state of a method passed to a mocked method call. I use it in the following cases DAO method, like create or update is called in the code. I want to check, if the entity has been set correctly before writing into… Continue reading Checking parameter of a mocked method call with Mockito
Category: JUnit
Create Spring service used only in test environment
Create Spring service used only in test environment In my project, we use three different environments for running the application. Production SIT (system integration) Local development In the production environment thee is a third party system, that authenticates the user and automatically adds a header value to the request. I wanted to implement a feature,… Continue reading Create Spring service used only in test environment
Using reflection in setup phase of unit testing
It is a common practice to use mock framework in the setup phase of a unit test, in order to set the internal state of the dependent objects. Sometimes it is though easier to set a value of a given field directly, in order to test the class accordingly. For modifying field value via reflection,… Continue reading Using reflection in setup phase of unit testing
How to use @Rule annotation instead of the expected keyword to unit test exceptions
The usual way for unit testing expected exceptions looks like this: @Test(expected = ConfigurationException.class) It has although the following disadvantages: you can not check details of the exception, like message or cause you can not do anything with the exception It is a better solution to use the @Rule annotation from JUnit. import org.hamcrest.core.StringContains; import org.junit.Assert;… Continue reading How to use @Rule annotation instead of the expected keyword to unit test exceptions