finding error thrown during cucumber execution about cucumber-java-skeleton HOT 6 CLOSED

Hello ssneha345 and welcome!
For questions please one of the support options.
GitHub issues are used to report bugs or request features.

from cucumber-java-skeleton.

From the example provided, you have an interesting way of running Cucumber.
Common usage would be to run Cucumber from the command line, using class Main and providing the options as arguments.
Could you explain why you would only want to see the error only after the run? If your driver initialization fails (as per your example), wouldn't you want your test to fail right away?

from cucumber-java-skeleton.

you are right..if there is some error say for driver initialization test should fail right away..which is happening..but i also want to know why the test fail , may be with the help of some exception thrown or just like in junit.result we have result.getFailures(), via which we can know the failure and its reason.

from cucumber-java-skeleton.

if i can get the exception thrown from the cucumber code in the @after method of hooks. i think that will also satisfy my need.

from cucumber-java-skeleton.

@ssneha345 Ok, do I understand correctly that you want to know why it failed?
Afaik I get a stack trace in my console when running tests locally and they fail. I'm running my test from a JUnit runner (like the RunCukesTest in this example project). Could you give that a try, please?

from cucumber-java-skeleton.

I'm closing this since it's a question and not a bug report or feature request.

from cucumber-java-skeleton.