forked from vividus-framework/vividus
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[plugin-csv] Respect CSV format configuration by step saving CSV to v…
…ariable (vividus-framework#4999)
- Loading branch information
Showing
3 changed files
with
15 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
Meta: | ||
@epic vividus-plugin-csv | ||
|
||
Scenario: Validate step: "When I save CSV `$csv` to $scopes variable `$variableName`" with non-default delimiter char | ||
Given I initialize scenario variable `csv-as-string` with value `key1;key2;key3 | ||
val1-1;val1-2;val1-3 | ||
val2-1;val2-2;val2-3` | ||
When I save CSV `${csv-as-string}` to scenario variable `csv` | ||
Then `${csv[1].key2}` is equal to `val2-2` |