JPA Attribute Converters provide an easy way to define how an entity attribute gets persisted to the database. You can use them to implement lots of different features, e.g. to encrypt your data as I showed in a previous post: How to use a JPA Attribute Converter to encrypt your data
But writing the Attribute Converter is not enough. We also need to make sure, that it is working correctly.
In general, there are two ways to test a Attribute Converter. We could write a unit test to check, if the conversion works correctly. But a unit test performs a test of the isolated class without putting it into the real execution environment. That means that we will still not know, if the converter works in one of our applications. If everything is set up correctly, the persistence provider will call the converter before writing to and after reading from the database. So we also need to check if the Attribute Converter gets called by the persistence provider and if everything works fine under that condition. We need to test the converter inside of the container we want to use for our application.
We will have a look at how this can be done with Arquillian and its persistence extension.
Something about Arqillian
If you are already familiar with Arquillian, you can skip this part. For all of you who have never worked with Arquillian so far, I just want to give some basic information. You can find a more detailed description at the Arquillian Getting Started guide.
Arquillian is a test framework for in container testing. The idea is to do not mock the container you want to use but to test your code inside of it. This provides the advantage, that you can test if your code will also work in your execution environment and not only in your mocked up test scenario. Arquillian provides lots of functionality to manage the container, inject required resources like EJBs or an EntityManager and make your live much easier.
The Arquillian tests are executed by junit. This is great, because you can use them everywhere, where you can execute junit tests. And that means in your IDE, as part of your build process, on your CI server, simply everywhere.
Object under test
The following code snippet shows the object under test for this example. It is a Attribute Converter that encrypts and decrypts a String attribute. The converter gets called by the persistence provider before writing to and after reading from the database. If you want to read more about how this Attribute Converter works, check my posting about it.
Setting it up
Before we can start to write our tests, we need to define a few dependencies. I will only show how to configure the dependencies we need for this example. If you have not already set up arquillian tests for your project, you will have to do a little bit more. Please check the Getting Started guide to learn how to setup arquillian for your project. Don’t be afraid, there is not too much to do.
As you can see in the following snippet, we will use JUnit 4.11, Arquillian 1.1.3.Final, the Arquillian Persistence Extension 1.0.0.Alpha7 and the WildFly Application Server 8.1.0.Final.
Writing the tests
There are two things we need to do to setup our test environment. At first, we need to tell junit that this test shall be executed as a junit test. This is done by
Additionally, we need to create the test deployment, that will be deployed to the container. Therefore we need to implement at least one method and annotate it with
@Deployment. As you can see in the following code snippet, we use ShrinkWrap to create a jar archive deployment. The archive contains the
CreditCard entity, the
CryptoConverter Attribute Converter and the test class. There is no need to include any EJBs or other classes which implement business logic. We can inject the EntityManager into our test case and use it directly to persist and read entities. We will have a more detailed look at it later on.
Additionally, we need to add some manifest resources to create a persistence unit, register the Attribute Converter and add an empty beans.xml to activate CDI. Please check the getting started guide to get more information on ShrinkWrap and creating deployments.
After this is done, we can start to write the test cases. At first, we will persist a
CreditCard entity and check, if the credit card number gets encrypted by the
CryptoConverter. Therefore we inject the EntityManager, create a
CreditCard entity and pass it to the persist method of the EntityManager. The validation of the persisted data, is done by the Arquillian persistence extension. We just need to define the data we expect to be written to the database. The expected data is defined in the cc.yml file, which is referenced in the
@ShouldMatchDataSet annotation. Because the id attribute is generated by the database, we want to exclude it from the validation. This can be done by referencing it in the excludeColumns attribute of the annotation.
The cc.yml contains the following information.
In the second test, we will check if we can search the database for a
CreditCard entity with a given credit card number. Therefore we use the
@UsingDataSet annotation to seed the database with data defined in the cc.yml file. Now we can use the injected EntityManager to call a named query to search for
CreditCard entity with the given number.
We used Arquillian and the Arquillian Persistence extension to test a JPA Attribute Converter. Therefore we injected the EntityManager and used the annotations
@UsingDataSet to validate and seed the database with a yml file.
If you want to try it yourself, you can find the sources on github.
You can run it by calling: git clone https://github.com/thjanssen/JPA2.1.git && cd JPA2.1/CryptoConverter && mvn test
What are your experiences with testing your Java EE application with Arquillian? Please write a comment about it.
Want to learn more about Arquillian, see the Arquillian Guides: http://arquillian.org/guides/
This post was originally published on the Arquillian blog.