Skip to content
This repository has been archived by the owner on Jul 17, 2020. It is now read-only.

Merge reports is removing Categories assigned for the tests in first report #837

vamsimadaka opened this issue Apr 1, 2017 · 2 comments


Copy link

merged report - categories view
after merge - report - categories of first run tests removed out
first run report - categories view


I'm using TestNGITestListener for extent reports. Using parent and child nodes. Extent reports Version 3.0.1.
Setting the categories to the child tests.
When I'm merging 2 reports - then the categories set for the tests executed in first report are getting removed after merge. I can see only categories of the tests executed during 2nd run.

Expected Behavior

Categories of the first run tests should retain.

Current Behavior

Categories of the 2nd run tests only showing up in the merged report.

Environment Details

  • Extent report Version used: 3.0.1
  • Operating System and version: Window7 64 bit
  • JDK Version: 1.8.0_121


Copy link

rdivahar commented Oct 19, 2017

Hi @anshooarora ,

I am using the latest version (3.0.7) of extent-reports, and I am encountering exactly the same issue as @vamsimadaka .


I am merging two reports using htmlReporter.setAppendExisting(true); and it works with no issues except the merging of tests based on category. The category section only has the tests that is associated with the second report and missing the tests from the first report. Whereas, the other sections displays the results of all the tests.

Expected Behavior:

The category section should display the all tests. Both from the first report + second report with the corresponding category tag.


The category section only shows up the tests from the latest appended report (2nd @report). Attached screenshots below.

Dashboard View:


Category View:

Category view doesn't display up all the tests (merged), instead it shows up only the tests that is associated with the last appended tests from the second report.


Copy link

SwathiReddygovind commented Dec 5, 2017

Hi Divahar
Did you get the soultion @rdivahar .Even I am facing the same issue in 3.0.3.

If it is fixed please tell me solution.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

4 participants