Skip to content

Latest commit

 

History

History
87 lines (65 loc) · 2.23 KB

plugin-csv.adoc

File metadata and controls

87 lines (65 loc) · 2.23 KB
Raw

CSV Plugin

The plugin provides the ability to work with CSV files.

Properties

Property Name Acceptable values Default Description

csv.delimiter-char

<char>

,

The char used for value separation, must not be a line break character

csv.escape-char

<char>

<disabled: no escape char>

The char used to escape special characters in values, may be disabled

Table Transformers

Note
 The table transformers properties marked with bold are mandatory.

FROM_CSV

FROM_CSV transformer generates table from the given CSV file.

Parameter Description

csvPath

The relative path of the CSV file

delimiterChar

The char used for value separation, must not be a line break character

If delimiterChar is not set, then the corresponding property will be used during parsing.

The transformer based on the default configuration
{transformer=FROM_CSV, csvPath=/data/example.csv}
The transformer with custom inlined configuration
{transformer=FROM_CSV, csvPath=/data/another-example.csv, delimiterChar=;}

Steps

Save CSV into variable

Saves CSV string to indexed zero-based variable with column name mappings, e.g. var[0].key2, var[1].key1 etc. Please see the documentation for more information about complex variables.

When I save CSV `$csv` to $scopes variable `$variableName`

  1. $csv - CSV string.

  2. $scopes - The comma-separated set of the variables scopes.

  3. $variableName - The name of the variable to save CSV string.

Validate CSV data
Given I initialize scenario variable `csv` with value `key1,key2,key3
val1-1,val1-2,val1-3
val2-1,val2-2,val2-3`
When I save CSV `${csv}` to scenario variable `expected-csv`
When I save CSV `#{loadResource(/data/simple-csv.csv)}` to scenario variable `actual-csv`
Then `${expected-csv}` is equal to `${actual-csv}`
Then `${csv-from-file[1].key2}` is equal to `val2-2`