JBehave
  1. JBehave
  2. JBEHAVE-737

Improve table usage on steps in parameterized scenarios

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.5.4
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Number of attachments :
      1

      Description

      The NamedParameters from the Examples section of a parameterized scenario can be use to replace values in a table used in a step in that scenario. The current replacement scheme is to replace the value whereever it appears in the table data. This improvement is to offer an option to replace table data where the value matches the named parameter as the whole value. It is also to change the algorithm on all replacement to process the named parameters in a sorted order (largest to smallest in length) so as to avoid replacement where one parameeter name is part of another parameter name.

      The default behaviour is to do full replacement (as is currently the case). This behaviour can be overridden via ParameterControls (a replaceWholeWordValue property) or on a per-table basis (with

      {replaceWholeWordValue=true|false}

      ).

      An updated parameterised_table.story is attached with expected behaviour.

        Activity

        There are no entries against this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Brian Repko
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: