The location abstraction for test steps from scenario outlines is too limited

[brasmusson]

Summary

The location abstraction for a test step from a scenario outline is too limited. Both the location of the outline step and the example table row instantiating the scenario outline is relevant for a test step and should be easily accessible from the test step. A Pickle steps created by the Gherkin compiler for steps of scenario outlines contains both the location of the outline step and the location of the example table row instantiating the scenario outline.

Expected Behavior

Cucumber-Ruby-Core should support that both the location of the outline step and the example table row instantiating the scenario outline is easily accessible, by for instance formatters, of test steps from scenario outlines.

Current Behavior

Currently Cucumber-Ruby-Core defines the single location of a test steps from scenario outlines as the location of the example table row instantiating the scenario outline. This has caused a regression compared to Cucumber-Ruby v1.x.x in both the Pretty Formatter and the Json Formatter (see cucumber/cucumber-ruby#1108).

Possible Solution

For instance define a method #original_location that for ExpandedOutlineSteps return the location of the OutlineStep it was expanded from, and that for Steps return the same location as the #location method.

Steps to Reproduce (for bugs)

See cucumber/cucumber-ruby#1108.

Context & Motivation

To be able to fix the regressions from Cucumber-Ruby v1.x.x.

Note

Also for test cases from scenario outlines the location abstraction similarly limited, but that is not causing any regressions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.