Custom Formatters

As Cucumber runs your features, it calls out to any number of listener objects to let them know how it’s progressing. These listeners are notified at various points throughout the run of features. You can visualise this by using the ‘debug’ formatter. For example, take this simple feature in Cucumber’s own test suite:

$ head -7 examples/self_test/features/sample.feature
# Feature comment
@one
Feature: Sample

    @two @three
  Scenario: Missing
    Given missing

Here are the events fired to a listener, shown using the debug formatter:

$ cucumber —format debug examples/self_test/sample.feature:6

before_features

  before_feature

    before_comment

      comment_line

    after_comment

    before_tags

      tag_name

    after_tags

    feature_name

    before_feature_element

      before_tags

        tag_name

        tag_name

      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

If you want to write your own custom formatter, just create a class that implements any of the methods you see in the output from the debug formatter. Let’s illustrate this with an example.

Maybe you want to create a formatter that posts a message to Twitter every time a step fails? (I’m sure that would get you a lot of followers).

Here is how you’d do that:

Save your custom formatter class in features/support (or if you want to put it elsewhere, put a file in that directory that requires your formatter class).

# features/support/twitter_formatter.rb
require 'rubygems'
require 'twitter'

module Silly
  class TwitterFormatter
    def initialize(step_mother, io, options)
      # We don't care about these - we're just twittering!
    end

    def step_name(keyword, step_match, status, source_indent, background)
      if status == :failed
        step_name = step_match.format_args(lambda{|param| "*#{param}*"})
        message = "#{step_name} FAILED"
        Twitter::Base.new('your email', 'your password').post(message)
      end
    end
  end
end

Now you can run your features by passing --format Silly::TwitterFormatter to the cucumber command line, Rake task or even in cucumber.yml – see Running Features for all the options. You have more methods available than the ones used in this awesome example (but you only need to implement the ones you care about). Look at the sources for some of Cucumber’s built-in formatters to discover more methods.

If your formatter can’t be found

If cucumber complains that it can’t find your formatter, add an explicit --require dir, where dir is a parent directory of your formatter. You can also pass the full path to the ruby file where the formatter is defined.

The cucumber --help states:

Automatic loading is disabled when this option is specified, and all loading becomes explicit. Files under directories named “support” are always loaded first.

This means that you have to add your support folder to --require dir for it to be loaded.

Other Formatters

1. TeamCityFormatter: prints cucumber results in a format for interpretation by a TeamCity build agent
2. TextmateFormatter: prints cucumber results as HTML with enhanced styling and Javascript for Textmate (Included in the cucumber core since 0.4.5)
3. cucumber-json – A cucumber output formatter that outputs JSON
4. SlowHandCuke – Simple tweak to the Pretty formatter to display the currently running step as it is running
5. timestamped-scenarios – Append test run timestamps to each scenario name as it is being output.
6. Fuubar – The instafailing progress bar formatter
7. Viewcumber – Cucumber formatter which generates an HTML website to browse your scenarios and view screen capture of every single step.