[More Detail] [Collapse All]
Feature: Displaying Scenarios
# Comments that appear before the feature are associated with the feature
As a reader of the documentation I expect that scenario are documented correctly
example/scenario.feature
- Background:
link
# Comments after the feature description belong to the background or first scenario
example/scenario.feature:7
Given this background step
 
- Scenario: No Step Scenario
link
example/scenario.feature:11
No Steps Defined
- Scenario: Scenario With Steps
link
example/scenario.feature:14
Given this first step
 
When this second step
 
Then this third step
 
- Scenario: Optional Parameter Step Definition
link
example/scenario.feature:20
# This step definition has some optional parameters
Given a project
 
And an inactive project
 
And a project with the name 'optional', start date 10/26/2010, nicknamed 'norman'
 
- Scenario: Matched Term Highlighting
link
example/scenario.feature:27
Given a duck that has a bill
 
Then I expect the duck to quack
 
- Scenario: Scenario With Table
link
example/scenario.feature:32
Given the following table:
column 1 column 2 column 3
value 1 value 2 value 3
- Scenario: Scenario With Text
link
example/scenario.feature:38
Given the following text:
Oh what a bother!
That this text has to take up two lines
  This line should be indented 2 spaces
    This line should be indented 4 spaces      
- Scenario: Scenario with comments and a description
link
There once was a need for information to be displayed alongside all the
entities that I hoped to test
# Comments before the scenario
example/scenario.feature:49
# First Comment
Given this first step
 
# Second Comment that
# spans a few lines
And this second step
 
# Third Comment
And this third step
 
- Scenario: Step ending with a match with double-quotes
link
# Comments after the last step, where do they go?
example/scenario.feature:61
When searching the log for the exact match of the message "Entering application."
 
When the step definition has HTML escaped characters like: "<>&"