Sha256: ae58b9729adc665e288ee03c95981c295583ca8e747739352a0c43a792b4b150

Contents?: true

Size: 1016 Bytes

Versions: 3

Compression:

Stored size: 1016 Bytes

Contents

Feature: Debug formatter

  In order to help you easily visualise the listener API, you can use
  the `debug` formatter that prints the calls to the listener as a
  feature is run.

  Background:
    Given the standard step definitions

  Scenario: title
    Given a file named "features/test.feature" with:
      """
      Feature:
        Scenario:
          Given this step passes
      """
    When I run `cucumber -f debug`
    Then the stderr should not contain anything
    Then it should pass with:
      """
      before_features
        before_feature
          before_tags
          after_tags
          feature_name
          before_feature_element
            before_tags
            after_tags
            scenario_name
            before_steps
              before_step
                before_step_result
                  step_name
                after_step_result
              after_step
            after_steps
          after_feature_element
        after_feature
      after_features
      """

Version data entries

3 entries across 3 versions & 1 rubygems

Version Path
cucumber-2.0.0.beta.3 features/docs/formatters/debug_formatter.feature
cucumber-2.0.0.beta.2 features/docs/formatters/debug_formatter.feature
cucumber-2.0.0.beta.1 features/docs/formatters/debug_formatter.feature