Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect scenario count for tags and categories is displayed #5

Closed
darkPanther2628 opened this issue Mar 5, 2022 · 5 comments
Closed

Comments

@darkPanther2628
Copy link

No description provided.

@grasshopper7
Copy link
Owner

provide a concrete example and related feature files. thx

@darkPanther2628
Copy link
Author

darkPanther2628 commented Mar 5, 2022

I have 2 feature files and 4 scenario's that has to be executed. I have added extentreports-cucumber7-adapter as a maven dependency to my project.

My report is showing the scenario's and feature count correctly but scenario count in tags and categories is incorrect.
Please find below screenshot

I have 4 scenario's but the report shows 8 in total in Tags/categories section

Please find the code in following repository
https://github.com/darkPanther2628/BDDTesy.git

image
image

Runner File config :
image

@grasshopper7
Copy link
Owner

This is a known issue for which a fix is required in the core Extent report code.
Each feature, scenario and scenario outline are converted into Extent Tests. The tag information is cascaded for all the extent tests in the hierarchy. For the @smokeTests tag you will have 2 tests from login.feature and 2 from the login2.feature.

@AlexBravo95
Copy link

AlexBravo95 commented Apr 13, 2022

Good morning, dear, I have the same problem. I think that to avoid noise in the client, I will remove the tag from the report.

Thank you and good job with the library

@grasshopper7
Copy link
Owner

This has been fixed in version 1.7.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants