Brian Repko created JBEHAVE-737:
-----------------------------------
Summary: Improve table usage on steps in parameterized scenarios
Key: JBEHAVE-737
URL: https://jira.codehaus.org/browse/JBEHAVE-737
Project: JBehave
Issue Type: Improvement
Components: Core
Affects Versions: 3.5.4
Reporter: Brian Repko
Attachments: parametrised_table.story
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
