adaklabs JUnit5 Integration
The repository contains JUnit5 Extension for adaklabs integration.
To start using adaklabs with JUnit 5 create a service location file:
- Create folders /META-INF/services in resources
- Put there a file named org.junit.jupiter.api.extension.Extension
- Put a default implementation reference as a single row into the file: com.epam.reportportal.junit5.ReportPortalExtension
Example: /META-INF/services/org.junit.jupiter.api.extension.Extension
com.epam.reportportal.junit5.ReportPortalExtension
If you desire to configure test name, description and tags:
Extend ReportPortalExtension, override buildStartStepRq() or other methods (see javadoc comments) and replace com.epam.reportportal.junit5.ReportPortalExtension with fully qualified custom Extension class name in this file.
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>agent-java-junit5</artifactId>
<version>5.1.4</version>
</dependency><build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<properties>
<configurationParameters>
junit.jupiter.extensions.autodetection.enabled = true
</configurationParameters>
</properties>
</configuration>
</plugin>
</plugins>
</build>repositories {
mavenLocal()
mavenCentral()
}
testCompile 'com.epam.reportportal:agent-java-junit5:5.1.4'test {
useJUnitPlatform()
systemProperty 'junit.jupiter.extensions.autodetection.enabled', true
}By default reporting of @Disabled tests is switched off. To switch it on - add next parameter to an execution goal:
- Maven: -DreportDisabledTests=true
- Gradle: -PreportDisabledTests=true
This manual will walk you through the steps for integration of Report Portal with JUnit5 based project
We’ll assume that Report Portal is installed and running on http://localhost:8080
If you want to integrate Report Portal with existing project, go to step 2
adaklabs agent implementation for JUnit 5
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>agent-java-junit5</artifactId>
<version>5.1.4</version>
</dependency>Latest version of the agent, could be found here
The adaklabs agent for JUnit 5 includes the JUnit 5 library dependency, and so we won't need other explicit JUnit 5 dependencies
However, if you are adding Report Portal agent to existing project, with JUnit 5 dependency already declared, pay attention to dependency transitivity and the conflicts that might arise
More about JUnit 5 dependencies structure could be found here
adaklabs provides it's own logger implementation for major logging frameworks like log4j and logback
If you prefer using Logback logging library, add following dependencies:
ADAKLABS logback logger dependency
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>logger-java-logback</artifactId>
<version>5.1.1</version>
</dependency>Up to date version could be found here
The logback itself
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.2.10</version>
</dependency>If you prefer using Log4j logging library, add following dependencies:
ADAKLABS log4j logger dependency
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>logger-java-log4j</artifactId>
<version>5.1.4</version>
</dependency>Up to date version could be found here
The log4j itself
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.17.1</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.17.1</version>
</dependency>Create a test class MyTests in the test directory and add JUnit 5 test method there
package com.mycompany.tests;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.junit.jupiter.api.*;
public class MyTests {
private static final Logger LOGGER = LogManager.getLogger(MyTests.class);
@Test
void testMySimpleTest() {
LOGGER.info("Hello from my simple test");
}
}Example:
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN">
<Appenders>
<Console name="ConsoleAppender" target="SYSTEM_OUT">
<PatternLayout
pattern="%d [%t] %-5level %logger{36} - %msg%n%throwable"/>
</Console>
<ReportPortalLog4j2Appender name="ReportPortalAppender">
<PatternLayout
pattern="%d [%t] %-5level %logger{36} - %msg%n%throwable"/>
</ReportPortalLog4j2Appender>
</Appenders>
<Loggers>
<Root level="DEBUG">
<AppenderRef ref="ConsoleAppender"/>
<AppenderRef ref="ReportPortalAppender"/>
</Root>
</Loggers>
</Configuration>It's needed to add ADAKLABSAppender into this (as shown in the example)
By this moment, your project tree should look somewhat like the this:
Go to http:$IP_ADDRESS_OF_REPORT_PORTAL:8080 (by default it is http://localhost:8080)
Go to Administrative -> My Test Project -> Members -> Add user
Example link http://localhost:8080/ui/#administrate/project-details/my_test_project/members
After you have created new user in your project, you can get ADAKLABS.properties file example from the user Profile page
To do that, login as created user and go to User icon in header -> Profile
There, in Configuration Examples section, you can find the example of ADAKLABS.properties file for that user
Returning back to the code. In your project, create file named ADAKLABS.properties in resources folder and copy&paste the contents form the user profile page
Example:
[ADAKLABS.properties]
rp.endpoint = http://localhost:8080
rp.uuid = d50810f1-ace9-44fc-b1ba-a0077fb3cc44
rp.launch = jack_TEST_EXAMPLE
rp.project = my_test_project
rp.enable = trueMore details on
ADAKLABS.propertiesfile could be found here
There are two options how you can enable ADAKLABS extension in your tests:
- By specifying
@ExtendWithannotation - By service location
Each test marked with @ExtendWith(ADAKLABSExtension.class) will be reporter to ADAKLABS.
This is an inheritable annotation, that means you can put it on a superclass and all child classes will
also use a specified extension.
For example:
import com.epam.reportportal.junit5.ReportPortalExtension;
import org.junit.jupiter.api.extension.ExtendWith;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.EnumSource;
@ExtendWith(ReportPortalExtension.class)
public class EnumParametersTest {
public enum TestParams {
ONE,
TWO
}
@ParameterizedTest
@EnumSource(TestParams.class)
public void testParameters(TestParams param) {
System.out.println("Test: " + param.name());
}
}For those who implement their own custom extensions we decided to remove /META-INF/services file from our project.
To use our standard non-custom extension you need to add this file into your project by yourself.
To do that create a file named org.junit.jupiter.api.extension.Extension in src/test/resources/META-INF/services folder
with the following content:
com.epam.reportportal.junit5.ReportPortalExtension
As a final step you need to tell JUnit to register our Report Portal agent, and there are multiple ways for doing that:
- method 1 - via Maven Surefire/Failsafe plugin (maven only)
- method 2 - via JVM system property
- method 3 - via
junit-platform.propertiesfile - method 4 - via Gradle (gradle only)
Add a build section and Maven Surefire plugin with the following configuration section to pom.xml
<build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<properties>
<configurationParameters>
junit.jupiter.extensions.autodetection.enabled = true
</configurationParameters>
</properties>
</configuration>
</plugin>
</plugins>
</build>The junit.jupiter.extensions.autodetection.enabled = true configuration parameter of the Surefire plugin links Report Portal agent with the tests
Full pom.xml file example
[pom.xml]
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.mycompany</groupId>
<artifactId>MyProject</artifactId>
<version>1.0-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>agent-java-junit5</artifactId>
<version>5.1.4</version>
</dependency>
<dependency>
<groupId>com.epam.reportportal</groupId>
<artifactId>logger-java-log4j</artifactId>
<version>5.1.4</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.17.1</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.17.1</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<properties>
<configurationParameters>
junit.jupiter.extensions.autodetection.enabled = true
</configurationParameters>
</properties>
</configuration>
</plugin>
</plugins>
</build>
</project>Now the Report Portal agent is linked to your tests and when you run the tests with maven, the results should be sent to Report Portal
Important note. With this approach, only the tests executed via maven will be sent to Report Portal, while tests ran by IDE will not trigger the Report Portal agent and therefore the test-report won't be generated
To have test results to be sent to Report Portal when executed from IDE (without maven), follow the steps below
Another way to link test runs with Report Portal is to add JVM system property to the run arguments for test runs
Here is the example of adding run arguments with IntelliJ IDEA
In Intellij IDEA go to Run -> Edit Configurations -> click on "+" sign -> select JUnit
Enter the name of the run, select classes and/or methods to be executed in this configuration and add the following line into VM Options field:
-Djunit.jupiter.extensions.autodetection.enabled=trueWhen you are done adding local run configuration, simply go to Run -> Run <test_run_name> and that test run results should be sent to Report Portal
There is another option of linking Report Portal with your JUnit 5 tests
Add junit-platform.properties file to your resources folder and add the following line there:
junit.jupiter.extensions.autodetection.enabled=true
More details about JUnit 5 extensions detection configuration could be found here
With this approach, the test report will be generated and sent to Report Portal in any type of test run, whether it was via maven, gradle or via IDE
Starting from gradle version 4.6 it provides native support for JUnit 5 tests via useJUnitPlatform(), more details here
Assuming that you have the gradle project setup, add/edit your test task in gradle.build file with the following code:
test {
testLogging.showStandardStreams = true
useJUnitPlatform()
systemProperty 'junit.jupiter.extensions.autodetection.enabled', true
}Please note, that using this method, the test report will be generated only if you ran your tests with Gradle (e.g.
gradle clean test)
Full build.gradle file example:
[build.gradle]
apply plugin: 'java'
sourceCompatibility = 1.8
targetCompatibility = 1.8
repositories {
mavenLocal()
mavenCentral()
}
dependencies {
compile 'com.epam.reportportal:logger-java-log4j:5.1.4'
compile 'org.apache.logging.log4j:log4j-api:2.17.1'
compile 'org.apache.logging.log4j:log4j-core:2.17.1'
compile 'com.epam.reportportal:agent-java-junit5:5.1.4'
}
test {
testLogging.showStandardStreams = true
useJUnitPlatform()
systemProperty 'junit.jupiter.extensions.autodetection.enabled', true
}After you linked the adaklabs JUnit 5 agent using one of the approaches described above and ran your tests, you should be able to see the results in your ADAKLABS UI instance
To do that, login to ADAKLABS, and go to Left Panel -> Launches
You should see the launch there, with the name equal to the value of rp.launch from your ADAKLABS.properties file
Example:
You can also see the test classes and individual test results by clicking on the launch name and going deeper
ehsan khashaee - Core service implementation - adak