Enhancement of #scenarioNameTemplate for scenario outlines

[pvoisin]

Today, given a scenario outline containing multiple scenarios, #scenarioNameTemplate (available as an option) would always be called once before the first scenario is even touched. Then, iteratively, for every scenario, it would not be called again at all. So, proposed changes include :

• Not calling #scenarioNameTemplate once before scenarios are actually iterated over;
• Call it after for every scenario in the outline;
• Passing feature, scenario and outline to the function for better control over the title it can produce (here, I only needed the ParsedScenario instance but since the other two are available they might be useful sometimes too).

Example feature:

Feature: Number Utility

  Scenario Template: with number <NUMBER> (<PRECISION>) → <RESULT>
    Given number <NUMBER>
    And precision <PRECISION>
    When #round is called
    Then result should be <RESULT>

    Examples:
      | NUMBER            | RESULT      | PRECISION |
      |             0.000 |           0 |           |
      |             1.255 |        1.26 |         2 |
      ...

For every scenario/example, scenarioTitle is today "with number <NUMBER> (<PRECISION>) → <RESULT>".
With proposed changes, this doesn't change but the actual scenario/example's title is reachable with scenario.title (which is, for example, "with number 0.000 () → 0" for the first scenario). FYI my name template is as follows:

scenarioNameTemplate: (variables) =>
      variables.scenarioTitle.replace('() →', '→'),

[pvoisin]

Hey @bencompton! Did you have a chance to check this out?

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[pvoisin]

@bencompton - Ping! ^^