allure2 | Allure Report is a flexible , lightweight multi | Dashboard library

Did you find an answer to your issue? I just had the same problem, and after hours of research, I fixed it by just reordering dependencies in pom.xml file: your dependencies to allure MUST be below your dependencies to browserMobProxy in the file... for a reason I can't explain.

So I think this would work for you:

The root cause was using both failsafe and surefire plugins, just had to remove one and now the tests only execute once.

Now its clear @ExtendedCucumberOptions were supported till Cucumber V 1.2.5 and Someone working on Cucumber 4.0.0 or later of V 1.2.5 shall not use this option in case someone like to re-run their failed test cases.

due to breaking changes in Cucumber API, for different versions of Cucumber JVM you will need different Allure adapters:

1. Cucumber JVM 1.x require allure-cucumber-jvm, formatter io.qameta.allure.cucumberjvm.AllureCucumberJvm
2. Cucumber JVM 2.x require allure-cucumber2-jvm, formatter io.qameta.allure.cucumber2jvm.AllureCucumber2Jvm
3. Cucumber JVM 3.x require allure-cucumber3-jvm, formatter io.qameta.allure.cucumber3jvm.AllureCucumber3Jvm
4. Cucumber JVM 4.x require allure-cucumber4-jvm, formatter io.qameta.allure.cucumber4jvm.AllureCucumber4Jvm

allure-maven plugins is responsible report generation and can be used together with any of adapters above

Update: I have created example project with Cucumber JVM 3.x + Allure 2 + Maven here: https://github.com/letsrokk/stackoverflow-examples/tree/master/allure-cucumber-example

You can either run tests and serve report straight away

You are probably using custom aop.xml configuration file thats excludes Allure aspects from weaving. Make sure that package io.qameta.allure is included in weaver configuration

JUnit Jupiter also supports registering extensions programmatically by annotating fields in test classes with @RegisterExtension:

Allure2 does support xunit project. It does not require special adapter. Allure2 has inbuilt plugin trx-plugin and xunit-xml-plugin. Steps taken for .netcore2 xunit test project using allure-commandline. (Refer docs to install allure commandline - docs.qameta.io/allure/latest/#_installing_a_commandline)

TRX report:

1. Generated output xunit trx report with command: dotnet test --logger:trx
2. Generated Allure report with command: allure serve /home/path/to/project/target/surefire-reports/

XML Report:

1. Add a reference to the Xunit Logger nuget package in test project.

2. Generate output xunit xml report with command: dotnet test --logger:xunit

3. Generated Allure report with command: allure serve /home/path/to/project/target/surefire-reports/

Allure 2 listeners are managed by SPI mechanism. So there're several steps you need to do to make it works:

• Implement StepLifecycleListener interface and override required methods.
• Create META-INF/services folders in your project's resources root.
• Create a new file by the full name of this interface in the above folder.
• Add the full path to your implementation class into this file.

You can find an example in the the following project: https://github.com/sskorol/allure2-testng-report/blob/master/src/test/resources/META-INF/services/io.qameta.allure.listener.StepLifecycleListener

More info about SPI: http://docs.oracle.com/javase/tutorial/sound/SPI-intro.html

The problem is that argLine is not applied when forkCount is 0.

If you really need to disable forking there is two ways to fix that problem:

1. Configure AspectJ Weaver in MAVEN_OPTS. In that case all the maven code will be weaved, so you may need to add extra aop.xml and specify classes/packages that need to be weaved.
2. Use AspectJ compiler plugin instead of weaver.