Anshoo Arora

@FrankBergemann like the other one, please use ExtentSparkReporter. For configuration, use: https://github.com/extent-framework/extentreports-cucumber4-adapter/blob/master/config/extent.properties#L8 ``` extent.reporter.spark.start=true extent.reporter.spark.config= extent.reporter.spark.out=test-output/SparkReport/ ```

@suri1990 This issue has been fixed in cucumber4 adapter v`1.0.12`. Please update your version and try again.

@grasshopper7 thank you for your research. The adapter needs to implement `StrictAware` to consume the status of `strict` flag. Please review the commit https://github.com/extent-framework/extentreports-cucumber4-adapter/commit/7b027b95d260fe5ced254b55ce67f7e7df746235. @suri1990 Published snapshot release to nexus,...

@grasshopper7 this is nothing to do with the adapter but the Extent API itself. It is configured to account for each "event" that is raised - in our case these...

@zuzeac 1. I am able to reproduce this 2. The 2 cases are grouped, so both "skipped" and "pending" will go inside the same block of code.

Partial fix was on the API side https://github.com/extent-framework/extentreports-java/issues/139

They should also be logged. Can you check with `1.0.12-SNAPSHOT`?

@zuzeac Please create a small project reproducing the issue so I can see the behavior. Did you check the below as per your original post: > the failed number of...

Everything should be logged, I am not sure why it isn't. For me, if 1 scenario fails, the rest still execute as they normally would, they are not skipped by...

Thanks, having a project to understand the scenario would help.