Cucumber reports getting overwritten when a new feature file is executed

Question

I am writing a test suite and have came across an issue. I am using cucumber and have defined multiple feature files. When I run the test pack the progress (html report and json format) of one feature file gets over-written when the next feature file execution begins.

I have multiple test classes defined that runs these feature files. I am trying to find a way I can get a single html report for all feature runs to give a consolidated view.

Sample test files for ref:

@CucumberOptions(plugin = { "pretty", "html:target/report/html",
"json:target/report/json/result.json" })
public class BaseFeature {

}

@RunWith(Cucumber.class)
@CucumberOptions(features = "classpath:test/feature/rest/query.feature"
, monochrome = true
, glue={"a.b.c.rest"})
public class RunTest1 extends BaseFeature {

}

@RunWith(Cucumber.class)
@CucumberOptions(features="classpath:test/feature/soap/book.feature"
, monochrome = true
, glue="a.b.c.soap")
public class RunTest2 extends BaseFeature {

}

Let know what can be done to have a consolidated report.

all your classes are suites, right? so a report can be generated for 1 suite at a time. — Avinash Anand, Jan 03 '17 at 04:15
Yes, because each RunWith Means seperate suite. So only 1 runner can be used at a time to generate report. Please provide your answer below to help someone else facing same problem in future. — Avinash Anand, Jan 04 '17 at 07:53

score 4 · Accepted Answer · answered Jan 16 '17 at 08:36

A bit late, but as committed I am posting the solution here. Cucumber has a maven plugin that can be used to generate reports.

<groupId>net.masterthought</groupId>
<artifactId>maven-cucumber-reporting</artifactId>
<version>${maven-cucumber-reporting.version}</version>

plugin version is currently : 3.3.0

This plugin provides some useful configuration parameters, that allows you to bind multiple test reports in json format.

A sample implementation is as follows:

<plugins> ...

  <plugin>
    <groupId>net.masterthought</groupId>
    <artifactId>maven-cucumber-reporting</artifactId>
    <version>${maven-cucumber-reporting.version}</version>
    <executions>
      <execution>
        <id>execution</id>
        <phase>verify</phase>
        <goals>
          <goal>generate</goal>
        </goals>
        <configuration>
          <projectName>test-report</projectName>
          <outputDirectory>${project.build.directory}/bdd/report</outputDirectory>
          <cucumberOutput>${project.build.directory}/report/json</cucumberOutput>
          <parallelTesting>false</parallelTesting>
        </configuration>
      </execution>
    </executions>
  </plugin>

</plugins>

Configuration to be used:

cucumberOutput: Path to where all the json reports are kept after the cucumber run outputDirectory: Path to where the html report will be generated

That's it and have fun.

score 1 · Answer 2 · answered Jan 07 '17 at 16:17

1

Like i said in comment above, merge your suite into 1, then you'll get 1 report. Since each RunWith means one suite, so basically use only 1 suite to get 1 report.

answered Jan 07 '17 at 16:17

Avinash Anand

655
2
15
25

1

I agree with the statement about Suite. But don't agree that it is the only way to get a central reports for the same, I will update with an answer for this today. – Himanshu Bhardwaj Jan 10 '17 at 06:17

Cucumber reports getting overwritten when a new feature file is executed

2 Answers2