Sha256: 57de55c5513b44d5d875a121f227bd6b709593ead9c3cc1862692cedc22b9e7d
Contents?: true
Size: 1.65 KB
Versions: 5
Compression:
Stored size: 1.65 KB
Contents
@gherkin
Feature: Table Row elements can be modeled.
Acceptance criteria
1. All conceptual pieces of a table row can be modeled:
- the row's source line
- the row's cells
- the row's raw element
2. Rows can be outputted in a convenient form
Background: Test file setup.
Given the following feature file:
"""
Feature:
Scenario:
* some data filled step:
| value 1 | value 2 |
| value 3 | value 4 |
* some data filled step:
| value 1 |
| value 2 |
"""
When the file is read
Scenario: The raw table row element is modeled.
Then the step table row correctly stores its underlying implementation
Scenario: The table row's source line is modeled.
Then step "1" table row "1" is found to have the following properties:
| source_line | 5 |
And step "1" table row "2" is found to have the following properties:
| source_line | 6 |
And step "2" table row "1" is found to have the following properties:
| source_line | 8 |
And step "2" table row "2" is found to have the following properties:
| source_line | 9 |
Scenario: The table row's cells are modeled.
Then step "1" table row "1" cells are as follows:
| value 1 |
| value 2 |
And step "1" table row "2" cells are as follows:
| value 3 |
| value 4 |
And step "2" table row "1" cells are as follows:
| value 1 |
And step "2" table row "2" cells are as follows:
| value 2 |
Scenario: Convenient output of a table row
Then the table row has convenient output
Version data entries
5 entries across 5 versions & 1 rubygems