In this post, let’s look at some of the Serenity maven artifacts useful in automation projects based out of Serenity, JBehave and Maven combination. These artifacts are typically added to pom.xml file of your project.

General steps are:
Add the dependencies to the automation project i.e pom.xml or build.gradle.
Update your project.

Serenity core:

Serenity core consists of core libraries and utility classes that provides services to initialize web testing and reporting-related fields. These classes are designed to help integrate Serenity into other testing tools such as Rest-Assured, Cucumber etc.

Maven repository:
https://mvnrepository.com/artifact/net.serenity-bdd/serenity-core/

serenity-junit is used for Serenity JUnit integration.

serenity-jbehave is used for Serenity JBehave integration. For example, class like SerenityStories that runs the JBehave stories, getting the class loader to obtain the JBehave and Step implementation classes etc.

serenity-jira-plugin is used for Serenity Jira integration. Some use cases that you might want to link jira issues in the Serenity reports. Adding comments on a Jira issue with the status of the tests run like pass/fail/pending etc.

pom.xml

<dependency>
<groupId>net.serenity-bdd</groupId>
<artifactId>serenity-core</artifactId>
<version>${serenity.version}</version>
</dependency>
<dependency>
<groupId>net.serenity-bdd</groupId>
<artifactId>serenity-junit</artifactId>
<version>${serenity.version}</version>
</dependency>
<dependency>
<groupId>net.serenity-bdd</groupId>
<artifactId>serenity-jbehave</artifactId>
<version>${serenity-jbehave}</version>
</dependency>
<dependency>
<groupId>net.serenity-bdd</groupId>
<artifactId>serenity-jira-plugin</artifactId>
<version>1.1.1</version>
</dependency>

 

These artifacts are the essential ones for working with automation using serenity and jbehave. There might be some other dependencies or plugins that i might have missed or over looked.