Sha256: ade8b87cd7f33004e2d6e5490a04c6b2838bcc21dfa288863108b3c751347713

Contents?: true

Size: 1.9 KB

Versions: 2

Compression:

Stored size: 1.9 KB

Contents

# Comments that appear before the feature are associated with the feature
@scenarios
Feature: Displaying Scenarios
  As a reader of the documentation I expect that scenario are documented correctly
  
  # Comments after the feature description belong to the background or first scenario
  Background:
    Given this background step

  @first
  Scenario: No Step Scenario

  @second
  Scenario: Scenario With Steps
    Given this first step
	When this second step
	Then this third step
	
  @third @optional_parameters
  Scenario: Optional Parameter Step Definition
    # 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'

  @fourth @highlight
  Scenario: Matched Term Highlighting
    Given a duck that has a bill
    Then I expect the duck to quack

  @fifth @table
  Scenario: Scenario With Table
    Given the following table:
      | column 1 | column 2 | column 3 |
      | value 1  | value 2  | value 3  |

  @sixth @text
  Scenario: Scenario With Text
    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 idented 4 spaces      
    """

  # Comments before the scenario
  @seventh @comments
  Scenario: Scenario with comments and a description
    There once was a need for information to be displayed alongside all the
    entities that I hoped to test
    # First Comment
    Given this first step
    # Second Comment that
    # spans a few lines
    And this second step
    # Third Comment
    And this third step
    # Comments after the last step, where do they go?

  Scenario: Step ending with a match with double-quotes
    When searching the log for the exact match of the message "Entering application."
    When the step definition has HTML escaped characters like: "<>&"

Version data entries

2 entries across 2 versions & 1 rubygems

Version Path
cucumber-in-the-yard-1.7.7 example/scenario.feature
cucumber-in-the-yard-1.7.6 example/scenario.feature