cucumber/cucumber — pull request #700 by brasmusson (2014-06-30 09:26:07+00:00)
Title: V1.3.x: Support the cucumber-reporting tools also when using Scenario Outlines

From reading the discussion in cucumber/gherkin#165, it is clear that people are pretty interested in being able to use the [cucumber-reporting](https://github.com/masterthought/cucumber-reporting) tools also together with Cucumber(-Ruby), see for instance [comment1](https://github.com/cucumber/gherkin/issues/165#issuecomment-39305022), [comment2](https://github.com/cucumber/gherkin/issues/165#issuecomment-42597176) and [commen3](https://github.com/cucumber/gherkin/issues/165#issuecomment-47215926) (the cucumber-reporting was initially developed to be used on Jenkins together with Cucumber-JVM).

The biggest obstacle to use it with Cucumber(-Ruby) is the very limited amount of information that end up in the JSON report for Scenario Outlines; no results, only the un-instantiated step (instead of the intantiated steps that actually was executed). One result of this problem is that the cucumber-reporting tools report "Result was missing for this step" (for the in-instantiated steps which are the only steps for the Scenario Outline included in the JSON report).

This PR changes the generated JSON report for Scenario Outlines when using the ```--expand``` option, to something the the cucumber-reporting tools can work on (that is, the same that Cucumber-JVM would have generated).

Fixes cucumber/gherkin#165.