{"id":12677,"date":"2013-08-10T18:47:00","date_gmt":"2013-08-10T17:47:00","guid":{"rendered":"https:\/\/touk.pl\/blog\/?guid=0111e52c5a78e32e2aeea278d9ed4fda"},"modified":"2022-08-03T09:27:02","modified_gmt":"2022-08-03T07:27:02","slug":"integration-tests-with-maven-and-junit","status":"publish","type":"post","link":"https:\/\/touk.pl\/blog\/2013\/08\/10\/integration-tests-with-maven-and-junit\/","title":{"rendered":"Integration tests with Maven and JUnit"},"content":{"rendered":"

There is no doubt that integration tests phase is crucial in modern applications development. We need to test behaviour of our subsystems and how they interact with other modules. Using JUnit and Maven it’s quite easy to create integration tests and run them in separate phase than unit test. It is very important, because integration tests tend to take much more time than unit ones because they work with database, network connections, other subsystems etc. Therefore, we want to run them more rarely. With JUnit in version >= 4.8 there are two approaches for creating and running integration test:
\n* using naming conventions and specifying separate executions for maven-surefire plugin
\n* create marking interface and mark integration tests with @Category annotation and run test from failsafe-plugin (although it is possible to use surefire in both cases)<\/p>\n

Separate executions First method needs naming convention like naming all unit tests with “..Test.java” postfix (or “..Spec.groovy” ;) and integration tests with “..IntegrationTest.java”. Then we need to change maven surefire configuration:<\/h3>\n
<plugin>\r\n    <groupId>org.apache.maven.plugins<\/groupId>\r\n    <artifactId>maven-surefire-plugin<\/artifactId>\r\n    <version>2.15<\/version>\r\n    <configuration>\r\n        <skip>true<\/skip>    \r\n    <\/configuration>\r\n<\/plugin>\r\n<\/pre>\n
What I did here is forcing maven to skip default test phase. Instead of that, I will configure two separate executions (just below the \u00a0section):<\/p>\n
<executions>\r\n    <execution>\r\n        <id>unit-tests<\/id>\r\n        <phase>test<\/phase>\r\n        <goals>\r\n            <goal>test<\/goal>\r\n        <\/goals>\r\n        <configuration>\r\n            <skip>false<\/skip>\r\n            <includes>\r\n                <include>**\/*Test.class<\/include>\r\n                <include>**\/*Spec.class<\/include>\r\n            <\/includes>\r\n            <excludes>\r\n                <exclude>**\/*IntegrationTest.class<\/exclude>\r\n            <\/excludes>\r\n        <\/configuration>\r\n    <\/execution>\r\n    <execution>\r\n        <id>integration-tests<\/id>\r\n        <phase>integration-test<\/phase>\r\n        <goals>\r\n            <goal>test<\/goal>\r\n        <\/goals>\r\n        <configuration>\r\n            <skip>false<\/skip>\r\n            <includes>\r\n                <include>**\/*IntegrationTest.class<\/include>\r\n            <\/includes>\r\n        <\/configuration>\r\n    <\/execution>\r\n<\/executions>\r\n<\/pre>\n
In unit test execution I include all test that match naming convention for unit tests (both JUnit and spock ones) and exclude files matching integration test pattern and in integration test execution I did something opposite ;)<\/p>\n
Annotations<\/h3>\n
Another method requires defining of marking interface like this:<\/div>\n
package info.rnowak.webtex.common.test;\r\n\r\npublic interface IntegrationTest {\r\n\r\n}\r\n<\/pre>\n
Then we can mark our integration test class with:<\/p>\n
@Category(IntegrationTest.class)\r\n<\/pre>\n
Next thing is changing of surefire plugin configuration to omit integration test:<\/p>\n
<plugin>\r\n    <groupId>org.apache.maven.plugins<\/groupId>\r\n    <artifactId>maven-surefire-plugin<\/artifactId>\r\n    <version>2.15<\/version>\r\n    <configuration>\r\n        <includes>\r\n            <include>**\/*Test.class<\/include>\r\n            <include>**\/*Spec.class<\/include>\r\n        <\/includes>  \r\n        <excludedGroups>info.rnowak.webtex.common.test.IntegrationTest<\/excludedGroups> \r\n    <\/configuration>\r\n<\/plugin>\r\n<\/pre>\n
What has changed here is new tag with name of interface which marks our integration tests. Next, we need to add and configure maven-failsafe plugin in order to run test from out integration test group:<\/p>\n
<plugin><plugin>\r\n    <groupId>org.apache.maven.plugins<\/groupId>\r\n    <artifactId>maven-failsafe-plugin<\/artifactId>\r\n    <version>2.15<\/version>\r\n    <executions>\r\n        <execution>\r\n            <goals>\r\n                <goal>integration-test<\/goal>\r\n            <\/goals>\r\n            <configuration>\r\n                <groups>info.rnowak.webtex.common.test.IntegrationTest<\/groups>\r\n                <includes>\r\n                    <include>**\/*.class<\/include>\r\n                <\/includes>\r\n            <\/configuration>\r\n        <\/execution>\r\n    <\/executions>\r\n<\/plugin>\r\n<\/pre>\n
With this configuration failsafe will run only test marked with @Category(IntegrationTest.class)<\/code>annotation, no matter what their names are.<\/p>\n
What is better? Well, in my opinion it’s just a matter of taste and style. Annotating each integration class may be a little cumbersome but we are not limited to naming classes within specified convention. On the other hand, unit test and integration test usually are named with some convention, so annotations are not a big deal.<\/h3>\n","protected":false},"excerpt":{"rendered":"There is no doubt that integration tests phase is crucial in modern applications development. We need to test behaviour of our subsystems and how they interact with other modules.Using JUnit and Maven it’s quite easy to create integration tests and run…\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[68,90,30],"class_list":{"0":"post-12677","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-development-design","7":"tag-java","8":"tag-maven","9":"tag-testing"},"_links":{"self":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/12677","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/comments?post=12677"}],"version-history":[{"count":5,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/12677\/revisions"}],"predecessor-version":[{"id":14898,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/posts\/12677\/revisions\/14898"}],"wp:attachment":[{"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/media?parent=12677"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/categories?post=12677"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/touk.pl\/blog\/wp-json\/wp\/v2\/tags?post=12677"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}