{"id":89689,"date":"2019-03-25T07:00:46","date_gmt":"2019-03-25T05:00:46","guid":{"rendered":"https:\/\/www.javacodegeeks.com\/?p=89689"},"modified":"2019-03-22T11:25:11","modified_gmt":"2019-03-22T09:25:11","slug":"maven-project-setup-mixing-spock-junit-5-tests","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2019\/03\/maven-project-setup-mixing-spock-junit-5-tests.html","title":{"rendered":"Maven Project Setup for Mixing Spock 1.x and JUnit 5 Tests"},"content":{"rendered":"

I create a sample Groovy project for Maven, that mixes Spock tests and JUnit 5 tests in one project. In the next section I\u2019ll describe how to set up such kind of Maven project.<\/p>\n

Enable Groovy in the Project<\/h3>\n

First at all, you have to enable Groovy in your project. One possibility is to add the GMavenPlus Plugin<\/a> to your project.<\/p>\n

\n
\n\n\n\n
\n
01<\/div>\n
02<\/div>\n
03<\/div>\n
04<\/div>\n
05<\/div>\n
06<\/div>\n
07<\/div>\n
08<\/div>\n
09<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n<\/td>\n
\n
\n
<<\/code>build<\/code>><\/code><\/div>\n
    <\/code><<\/code>plugins<\/code>><\/code><\/div>\n
        <\/code><<\/code>plugin<\/code>><\/code><\/div>\n
            <\/code><<\/code>groupId<\/code>>org.codehaus.gmavenplus<\/<\/code>groupId<\/code>><\/code><\/div>\n
            <\/code><<\/code>artifactId<\/code>>gmavenplus-plugin<\/<\/code>artifactId<\/code>><\/code><\/div>\n
            <\/code><<\/code>version<\/code>>1.6.2<\/<\/code>version<\/code>><\/code><\/div>\n
            <\/code><<\/code>executions<\/code>><\/code><\/div>\n
                <\/code><<\/code>execution<\/code>><\/code><\/div>\n
                    <\/code><<\/code>goals<\/code>><\/code><\/div>\n
                        <\/code><<\/code>goal<\/code>>addSources<\/<\/code>goal<\/code>><\/code><\/div>\n
                        <\/code><<\/code>goal<\/code>>addTestSources<\/<\/code>goal<\/code>><\/code><\/div>\n
                        <\/code><<\/code>goal<\/code>>compile<\/<\/code>goal<\/code>><\/code><\/div>\n
                        <\/code><<\/code>goal<\/code>>compileTests<\/<\/code>goal<\/code>><\/code><\/div>\n
                    <\/code><\/<\/code>goals<\/code>><\/code><\/div>\n
                <\/code><\/<\/code>execution<\/code>><\/code><\/div>\n
            <\/code><\/<\/code>executions<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>plugin<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>plugins<\/code>><\/code><\/div>\n
<\/<\/code>build<\/code>><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The goals addSources <\/em>and addTestSources <\/em>add Groovy (test) sources to Maven\u2019s main (test) sources. The default locations are src\/main\/groovy <\/em>(for main source) and src\/test\/groovy <\/em>(for test source). Goals compile <\/em>and compileTests <\/em>compile the Groovy (test) code. If you don\u2019t have Groovy main code, you can omit addSource <\/em>and compile<\/em>.<\/p>\n

This above configuration is always using the latest released Groovy version. If you want to ensure that a specific Groovy version is used, you have to add the specific Groovy dependency to your classpath.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
<<\/code>dependencies<\/code>><\/code><\/div>\n
        <\/code><<\/code>dependency<\/code>><\/code><\/div>\n
            <\/code><<\/code>groupId<\/code>>org.codehaus.groovy<\/<\/code>groupId<\/code>><\/code><\/div>\n
            <\/code><<\/code>artifactId<\/code>>groovy<\/<\/code>artifactId<\/code>><\/code><\/div>\n
            <\/code><<\/code>version<\/code>>2.5.6<\/<\/code>version<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>dependency<\/code>><\/code><\/div>\n
  <\/code><\/<\/code>dependencies<\/code>><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Enable JUnit 5 in the Project<\/h3>\n

The simplest setup for using JUnit 5 in your project is to add the JUnit Jupiter dependency in your test class path and to configure the correct version of Maven Surefire Plugin (at least version 2.22.0).

<\/div> <\/div><\/p>\n
\n
\n\n\n\n
\n
01<\/div>\n
02<\/div>\n
03<\/div>\n
04<\/div>\n
05<\/div>\n
06<\/div>\n
07<\/div>\n
08<\/div>\n
09<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n<\/td>\n
\n
\n
<<\/code>dependencies<\/code>><\/code><\/div>\n
<!--... maybe more dependencies --><\/code><\/div>\n
        <\/code><<\/code>dependency<\/code>><\/code><\/div>\n
            <\/code><<\/code>groupId<\/code>>org.junit.jupiter<\/<\/code>groupId<\/code>><\/code><\/div>\n
            <\/code><<\/code>artifactId<\/code>>junit-jupiter<\/<\/code>artifactId<\/code>><\/code><\/div>\n
            <\/code><<\/code>scope<\/code>>test<\/<\/code>scope<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>dependency<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>dependencies<\/code>><\/code><\/div>\n
 <\/div>\n
    <\/code><<\/code>dependencyManagement<\/code>><\/code><\/div>\n
        <\/code><<\/code>dependencies<\/code>><\/code><\/div>\n
            <\/code><<\/code>dependency<\/code>><\/code><\/div>\n
                <\/code><<\/code>groupId<\/code>>org.junit<\/<\/code>groupId<\/code>><\/code><\/div>\n
                <\/code><<\/code>artifactId<\/code>>junit-bom<\/<\/code>artifactId<\/code>><\/code><\/div>\n
                <\/code><<\/code>version<\/code>>${junit.jupiter.version}<\/<\/code>version<\/code>><\/code><\/div>\n
                <\/code><<\/code>scope<\/code>>import<\/<\/code>scope<\/code>><\/code><\/div>\n
                <\/code><<\/code>type<\/code>>pom<\/<\/code>type<\/code>><\/code><\/div>\n
            <\/code><\/<\/code>dependency<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>dependencies<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>dependencyManagement<\/code>><\/code><\/div>\n
    <\/code><<\/code>build<\/code>><\/code><\/div>\n
        <\/code><<\/code>plugins<\/code>><\/code><\/div>\n
        <\/code><!-- other plugins --><\/code><\/div>\n
            <\/code><<\/code>plugin<\/code>><\/code><\/div>\n
                <\/code><<\/code>artifactId<\/code>>maven-surefire-plugin<\/<\/code>artifactId<\/code>><\/code><\/div>\n
                <\/code><<\/code>version<\/code>>2.22.1<\/<\/code>version<\/code>><\/code><\/div>\n
            <\/code><\/<\/code>plugin<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>plugins<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>build<\/code>><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Enable Spock in the Project<\/h3>\n

Choosing the right Spock dependency depends on which Groovy version you are using in the project. In our case, a Groovy version 2.5. So we need Spock in version 1.x-groovy-2.5 in our test class path.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n<\/td>\n
\n
\n
<<\/code>dependencies<\/code>><\/code><\/div>\n
        <\/code><!-- more dependencies --><\/code><\/div>\n
        <\/code><<\/code>dependency<\/code>><\/code><\/div>\n
            <\/code><<\/code>groupId<\/code>>org.spockframework<\/<\/code>groupId<\/code>><\/code><\/div>\n
            <\/code><<\/code>artifactId<\/code>>spock-core<\/<\/code>artifactId<\/code>><\/code><\/div>\n
            <\/code><<\/code>version<\/code>>1.3-groovy-2.5<\/<\/code>version<\/code>><\/code><\/div>\n
            <\/code><<\/code>scope<\/code>>test<\/<\/code>scope<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>dependency<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>dependencies<\/code>><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now the expectation is that the Spock tests and the JUnit5 tests are executed in the Maven build. But only the JUnit5 tests are executed by Maven. So what happened?<\/p>\n

I started to change the Maven Surefire Plugin version to 2.21.0. Then the Spock tests were executed, but no JUnit5 tests. The reason is that in the version 2.22.0 of Maven Surefire Plugin JUnit4 provider is replaced by JUnit Platform Provider as default. But Spock in version 1.x is based on JUnit4. This will be changed in Spock version 2. This version will be based on the JUnit5 Platform. Thus, for Spock 1.x, we have to add JUnit Vintage dependency to our test class path.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n<\/td>\n
\n
\n
<<\/code>dependencies<\/code>><\/code><\/div>\n
        <\/code><!-- more dependencies --><\/code><\/div>\n
          <\/code><<\/code>dependency<\/code>>  <\/code><!--Only necessary for surefire to run spock tests during the maven build --><\/code><\/div>\n
            <\/code><<\/code>groupId<\/code>>org.junit.vintage<\/<\/code>groupId<\/code>><\/code><\/div>\n
            <\/code><<\/code>artifactId<\/code>>junit-vintage-engine<\/<\/code>artifactId<\/code>><\/code><\/div>\n
            <\/code><<\/code>scope<\/code>>test<\/<\/code>scope<\/code>><\/code><\/div>\n
        <\/code><\/<\/code>dependency<\/code>><\/code><\/div>\n
    <\/code><\/<\/code>dependencies<\/code>><\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

This allows running elder JUnit (3\/4) tests on the JUnit Platform. With this configuration both, Spock and JUnit 5 tests, are executed in the Maven build.<\/p>\n

Links<\/h3>\n