Details
Description
Named parameters, e.g. coming from the examples table in parametrised scenarios, should be optionally replaced in the row parameters values
Given a parametrised table:
| name | value |
| name1 | <scheme> |
Examples:
| <scheme> |
| scheme1 |
| scheme2 |
Values can be retrieved from the parameters row, using the option to replace named parameters:
boolean replaceNamedParameters = true; String value = table.getRowAsParameters(0, replaceNamedParameters).valueAs("value", String.class);
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Description |
Named parameters, e.g. coming from the examples table in parametrised scenarios, should be optionally replaced in the row parameters values
Given a parametrised table: |name|value| |name1|<scheme>| Examples: |<scheme>| |scheme1| |scheme2| |
Named parameters, e.g. coming from the examples table in parametrised scenarios, should be optionally replaced in the row parameters values
Given a parametrised table: |name|value| |name1|<scheme>| Examples: |<scheme>| |scheme1| |scheme2| Values can be retrieved from the parameters row, using the option to replace named parameters: {code} boolean replaceNamedParameters = true; String value = table.getRowAsParameters(0, replaceNamedParameters).valueAs("value", String.class); {code} |