Setup with Gradle
This quickstart shows you how to setup a new Citrus project with Gradle. After that you will be able to get Citrus tests running within minutes. You can find the project sources on GitHub citrus-samples/sample-gradle.
You need following software on your computer, in order to use the Citrus Framework:
- Java 11 or higher Installed JDK plus JAVA_HOME environment variable set up and pointing to your Java installation directory
- Java IDE A Java IDE will help you manage your Citrus project, create and execute test cases. Just use the Java IDE that you are used to (e.g. Eclipse or IntelliJ IDEA).
- Gradle 2.13 or higher Citrus tests will be executed with the Gradle build tool.
Citrus uses Maven internally for building software. But of course you can also integrate the Citrus tests in a Gradle project. Since Citrus tests are nothing but normal JUnit or TestNG tests, integration into your Gradle build is very easy.
First, we create a new Java project called citrus-sample. There are multiple ways to get started with a Gradle project. I personally prefer to use my Java IDE (IntelliJ) for generating a basic Gradle project setup. Of course there are lots of Gradle project start samples out there. And summing up the Gradle project structure is pretts simple so you could also create this manually. Here is the basic project structure that we are going to use in this quickstart.
citrus-sample | + src | | + main | | | + java | | | + resources | | + test | | | + java | | | + resources build.gradle settings.gradle
The Gradle build configuration is done in the build.gradle and settings.gradle files. Here we define the project name and the project version.
Now, since Citrus libraries are available on Maven central repository, we add these repositories so Gradle knows how to download the required Citrus artifacts.
Citrus stable release versions are available on Maven central. If you want to use the very latest snapshot version of Citrus you need to also add the ConSol Labs snapshot repository as server. This is optional and only applies if you want to use the snapshot versions of Citrus.
Now lets move on with adding the Citrus libraries to the project.
This enables the Citrus support for the project so we can use the Citrus classes and APIs. We decided to use TestNG unit test library.
Warning: This tutorial uses the TestNG unit test library. If you want to use JUnit, you will have to remove the above lines from your build.gradle file.
Of course JUnit is also supported. This is all for build configuration settings. We can move on to writing some Citrus integration tests. The Java test classes usually go to the src/test/java directory.
Lets write a simple Citrus test case in Java and save it to the src/test/java folder in package com.consol.citrus.samples.
This sample uses pure Java code for both Citrus configuration and tests. The Citrus TestNG test uses a context configuration annotation.
This tells Spring to load the configuration from the Java class EndpointConfig.
In the configuration class we are able to define Citrus components for usage in tests. As usual we can autowire the endpoint components as Spring beans in the test cases.
The sample application uses Gradle as build tool. So you can use the Gradle wrapper to compile, package and test the sample with Gradle build.
This executes all Citrus test cases during the build and you will see Citrus performing some integration test logging output. After the tests are finished build is successful and you are ready to go for writing some tests on your own.
If you just want to execute all tests you can call
Of course you can also start the Citrus tests from your favorite IDE. Just start the Citrus test using the Gradle integration in IntelliJ, Eclipse or Netbeans.
So now you are ready to use Citrus! Write test cases and add more logic to the test project. Have fun with it!