Test Run Results Reporting - Cucumber JSON

[darkhorse93]

Hi,

Have gone through docs, didn't find any thing on results reporting front. Is there anyway we can generate run result reports with all the test run features and their status.

Does jest-cucumber generate cucumber json file after every run where we can use it to generate HTML reports with the run results.

Thanks.

[bencompton]

Hi @darkhorse93. Reporting is out of scope for this library, and is instead accomplished with reporting plug-ins for Jest itself. For example, I have had a lot of success with jest-junit. Hope that helps!

[bencompton]

@darkhorse93 - if you're specifically asking about Cucumber JSON, I actually don't know of any current way to accommodate that with existing tooling. As far as HTML output, Pickles has worked fairly well for me for generating a searchable HTML page to publish as a living documentation website. Is something like this what you're ultimately trying to accomplish?

EDIT: For whatever reason, that example shows all of the tests as inconclusive, but I can confirm that when used in combination with jest-junit, Pickles output will actually show red and green for passing and failing tests.

Also, a similar question was also posed in #13, so while reporting is enabled via other tooling and is not part of jest-cucumber, it seems to be an important concern that would be worth covering in the docs.

[darkhorse93]

Thanks @bencompton for the clarification. We are currently using the jest-junit, and wanted cucumber style html reports . Thanks for your suggestion on pickles will look into it.

[kimthanhMillergold]

Hi , I have tried jest-cucumber but it always generate test report very general as follows
Feature
Scenario 1 : passed
Scenario 2: passed
How could i generate test report include steps and label which is passed or fail on steps ?

[bencompton]

@kimthanhMillergold, having detail beyond the scenario level is currently not supported. There will need to be a special plug-in for jest-cucumber to accomplish that.

[bencompton]

#27 is an enhancement in the backlog to address this, so closing this one.