Scenario Outline

Cucumber Extent Report v3.0.2

Hope everyone doing great. I’ve been busy with other things, hence I have neither written any article nor updated my library. But I’ve a quick update to everyone.

I’ve just released v3.0.2 of Cucumber Extent Report with a small bug fix (refer here). Thanks to Anshoo Arora for the quick pull request.

And I’ve been receiving queries often that the extent report class not found. As I mentioned in my previous article, you will have to explicitly add ExtentReport as a maven dependency. To do that, paste the following in your pom.xml:


Hope this answers many comments that I’ve received. And in case you have any issues, kindly open an issue in the github repo (

Going forward, I’ll be active on my blog and try to answer your queries.

3 Replies to “Cucumber Extent Report v3.0.2”

  1. Thank you very much for the update!!!Tired upgrading version from 3.0.1 to 3.0.2 shows error in pom.xml. Can you please let me know what could be wrong here….

  2. Hello Vimal, I have a question.

    I’m running my tests with Cucumber/Java and use AssertJ ( to perform soft assertions at tests various points, so that I can capture more than one failure at a time, if any. The problem I’m having is that AssertJ throws exceptions at the end of the test run whereas Cucumber Extent Report captured errors seems to be triggered only at the step level. In other words, while I do get AssertJ failures outlined in the surefire report and in console at test end, the generated report shows the test as passing.

    Is it there a way to trigger the fail message in Cucumber Extent Report at the end of the test run instead that at the step level? Is it there a failure method I can call before the report is generated thus changing the report to fail?

    Thank you

Comments are closed.