How to generate results from a ruby ​​cucumber scenario plan that can be properly consumed in cucumber reports?

We have an application that uses a cucumber with many cucumbers that use the outline of a script. We use ruby ​​to run tests.

I would like to show the results of these tests using cucumber-reporting . However, there is currently a problem with the way the results of the cucumber give JSON results (and others) for the scenario abstract, which means that the result does not contain the correct results, and the report cannot display these results. See this question and this question .

Is it possible to hack cucumbers so that the JSON report displays correctly when working with script outlines? Alternatively, is there an automated way to handle scenario outlines in normal scenarios so that the cucumbers generate proper reports?

Below I have a brute-force answer, but I would appreciate something less ragged.

+4
source share
1 answer

Note. I really don't like this answer.

cucumber -f pretty -x -d, , . , script, .

, , .

kludgy script -f pretty -x ( Examples: ).

Update:

- , , , : https://gist.github.com/blt04/9866357

+2

All Articles