jwilger-cucumber 0.3.11.200906161550

data/examples/tickets/features/270/back.steps.rb

@@ -0,0 +1,14 @@
+require 'spec/expectations'
+
+Given /^plop$/ do
+  raise "Only one plop!" if @plop
+  @plop = true
+end
+ 
+When /^I barp$/ do
+  @plop.should == true
+end
+ 
+When /^I wibble$/ do
+  @plop.should == true
+end

data/examples/tickets/features/272/hooks.feature

@@ -0,0 +1,26 @@
+@intentional_failure
+Feature: Hooks
+  In order to integrate with my complex environment
+  I need to check scenario status in an After block
+
+  @272_failed 
+  Scenario: Failed
+    Given I fail
+    
+  @272_undefined
+  Scenario: Undefined
+    Given I am undefined
+
+  @272_passed
+  Scenario: Passed
+    Given I pass
+    
+  @272_outline
+  Scenario Outline: Should work too
+    Given <something>
+    
+    Examples:
+      | something      |
+      | I fail         |
+      | I am undefined |
+      | I pass         |

data/examples/tickets/features/272/hooks_steps.rb

@@ -0,0 +1,53 @@
+require 'spec/expectations'
+
+Given /^I fail$/ do
+  raise "BOOM (this is expected)"
+end
+
+Given /^I pass$/ do
+end
+
+module HookChecks
+  def check_failed(scenario)
+    scenario.should be_failed
+    scenario.should_not be_passed
+    scenario.exception.message.should == "BOOM (this is expected)"
+  end
+
+  def check_undefined(scenario)
+    scenario.should_not be_failed
+    scenario.should_not be_passed
+  end
+
+  def check_passed(scenario)
+    scenario.should_not be_failed
+    scenario.should be_passed
+  end
+end
+
+World(HookChecks)
+
+After('@272_failed') do |scenario|
+  check_failed(scenario)
+end
+
+After('@272_undefined') do |scenario|
+  check_undefined(scenario)
+end
+
+After('@272_passed') do |scenario|
+  check_passed(scenario)
+end
+
+counter = 0
+After('@272_outline') do |scenario|
+  case(counter)
+    when 0
+      check_failed(scenario)
+    when 1
+      check_undefined(scenario)
+    when 2
+      check_passed(scenario)
+  end
+  counter +=1
+end

data/examples/tickets/features/279/py_string_indent.feature

@@ -0,0 +1,25 @@
+Feature: pystring indentaion testcase
+
+  Scenario: example of correct indentation
+    Given multiline string
+         """
+           I'm a cucumber and I'm ok
+         I sleep all night and test all day
+         """
+    Then string is
+      """
+        I'm a cucumber and I'm ok
+      I sleep all night and test all day
+      """						      
+
+  Scenario: example of wrong indentation
+    Given I am in tickets/features/279
+    When I run cucumber -q wrong.feature_
+    Then it should fail with
+      """
+
+      """
+    And STDERR should match
+      """
+      wrong.feature_:8:10: Parse error
+      """

data/examples/tickets/features/279/py_string_indent.steps.rb

@@ -0,0 +1,12 @@
+require 'spec/expectations'
+
+require File.dirname(__FILE__) + '/../../../../features/step_definitions/cucumber_steps.rb'
+require File.dirname(__FILE__) + '/../../../../features/support/env.rb'
+
+Given /^multiline string$/ do |string|
+  @string = string
+end
+
+Then /^string is$/ do |string|
+  @string.should == string
+end

data/examples/tickets/features/279/wrong.feature_

@@ -0,0 +1,11 @@
+Feature: pystring indentaion testcase
+
+  Scenario: example of wrong indentation
+    Given multiline string
+
+
+	 
+         """
+           I'm a cucumber and I'm ok
+         I sleep all night and test all day
+         """

data/examples/tickets/features/301/filter_background_tagged_hooks.feature

@@ -0,0 +1,6 @@
+Feature https://rspec.lighthouseapp.com/projects/16211/tickets/301
+  Background: A background
+    Given whatever
+    
+  Scenario: VB is not cool
+    Then VB should not be cool

data/examples/tickets/features/301/filter_background_tagged_hooks_steps.rb

@@ -0,0 +1,12 @@
+require 'spec/expectations'
+
+Before('@nothing_has_this_tag') do
+  @vb = :cool
+end
+
+Given /^whatever$/ do
+end
+
+Then /^VB should not be cool$/ do
+  @vb.should_not == :cool
+end

data/examples/tickets/features/306/only_background.feature

@@ -0,0 +1,4 @@
+Feature: woo yeah
+
+  Background:
+    Given passing step without a table

data/examples/tickets/features/lib/eatting_machine.rb

@@ -0,0 +1,18 @@
+class EattingMachine
+  
+  attr_reader :fruit_total, :belly_count
+  attr_accessor :belly_count
+  
+  def initialize(fruit_name, fruit_total)
+    @fruit_name = fruit_name
+    @fruit_total = fruit_total.to_i
+    @belly_count = 0
+  end
+    
+  def eat(count)
+    count = count.to_i
+    @fruit_total = @fruit_total - count
+    @belly_count += count
+  end
+      
+end

data/examples/tickets/features/lib/pantry.rb

@@ -0,0 +1,20 @@
+class Pantry
+
+  def initialize
+    @items = {}
+  end
+
+  def add(food_name, count)
+    @items[food_name] ||= 0
+    @items[food_name] += count.to_i
+  end
+
+  def remove(food_name, count)
+    @items[food_name] -= count.to_i
+  end
+
+  def count(food_name)
+    @items[food_name]
+  end
+
+end

data/examples/tickets/features/scenario_outline.feature

@@ -0,0 +1,95 @@
+Feature: Outlines
+  In order to re-use scenario table values
+  As a citizen of Cucumbia
+  I want to explicitly mark the parameters in a scenario outline
+
+  Scenario Outline: controlling order
+    Given there are <start> cucumbers
+    When I eat <eat> cucumbers
+    Then I should have <left> cucumbers
+
+  Examples:
+    | left  | start  | eat  |
+    |  7    |  12    |  5   |
+    |  15   |  20    |  5   |
+    
+  Scenario Outline: reusing place holder
+    Given there are <start> cucumbers
+    When I eat <eat> cucumbers
+    Then I should have <left> cucumbers
+    And I should have <eat> cucumbers in my belly
+
+  Examples: Lots of cukes
+    | start  | eat  | left |
+    |  12    |  5   |  7   |
+    |  20    |  5   |  15  |
+
+  Examples: Ridiculous amounts of cukes
+    | start  | eat  | left |
+    |  120    |  50   |  70   |
+    |  200    |  50   |  150  |
+  
+  Scenario Outline: no placeholders
+    Given there are 12 cucumbers
+    When I eat 5 cucumbers
+    Then I should have 7 cucumbers
+
+  Examples:
+    | start  | eat  | left |
+    |  12    |  5   |  7   |
+    |  20    |  5   |  15  |
+  
+  Scenario Outline: using '<' and '>' not as placeholder
+    Given the belly space is < 12 and > 6
+    And there are <start> cucumbers
+    When I eat <eat> cucumbers
+    Then I should have <left> cucumbers
+
+  Examples:
+    | start  | eat  | left |
+    |  12    |  5   |  7   |
+    |  20    |  5   |  15  |
+
+  Scenario Outline: with step tables
+    Given I have the following fruits in my pantry
+      |    name     | quantity |
+      | cucumbers   |    10    |
+      | strawberrys |    5     |
+      | apricots    |    7     |
+
+    When I eat <number> <fruits> from the pantry
+    Then I should have <left> <fruits> in the pantry
+
+    Examples:
+      | number |   fruits   | left |
+      |   2    | cucumbers  |  8   |
+      |   4    | strawberrys|  1   |
+      |   2    | apricots   |  5   |
+
+  Scenario Outline: placeholder in a multiline string
+    Given my shopping list
+      """
+        Must buy some <fruits>
+      """
+    Then my shopping list should equal
+      """
+        Must buy some cucumbers
+      """
+    
+    Examples:
+      |  fruits   |
+      | cucumbers |
+
+  Scenario Outline: placeholder in step table
+    Given I have the following fruits in my pantry
+      |    name     | quantity      |
+      | cucumbers   | <quant_cukes> |
+      | strawberrys | <quant_straw> |
+
+    When I eat <number> <fruits> from the pantry
+    Then I should have <left> <fruits> in the pantry
+
+    Examples:
+      | quant_cukes | quant_straw | number |   fruits    | left |
+      | 10          | 5           |   2    | cucumbers   |  8   |
+      | 5           | 5           |   4    | strawberrys |  1   |

data/examples/tickets/features/step_definitons/246_steps.rb

@@ -0,0 +1,3 @@
+Given /^no ([a-z]+(?: [a-z]+)*) exists in the system$/ do |resource|
+  resource.should == "public holiday"
+end

data/examples/tickets/features/step_definitons/248_steps.rb

@@ -0,0 +1,15 @@
+Given /^this is pending until we fix it$/ do
+  pending
+end
+
+Given /^context with Cheese$/ do
+  pending
+end
+
+When /^action$/ do
+  pending
+end
+
+Then /^outcome with Pepper Jack$/ do
+  pending
+end

data/examples/tickets/features/step_definitons/scenario_outline_steps.rb

@@ -0,0 +1,42 @@
+Given /^there are (\d+) (\w+)$/ do |count, fruit|
+  @eattingMachine = EattingMachine.new(fruit, count)
+end
+
+Given "the belly space is < 12 and > 6" do
+end
+
+Given "I have the following fruits in my pantry" do |pantry_table|
+  @pantry = Pantry.new
+  pantry_table.hashes.each do |item|
+    @pantry.add(item['name'].downcase, item['quantity'])
+  end
+end
+
+Given "my shopping list" do |list|
+  @shopping_list = list
+end
+
+When /^I eat (\d+) (\w+)$/ do |count, fruit|
+  @eattingMachine.eat(count)
+  @eattingMachine.belly_count = count.to_i
+end
+
+When /^I eat (\d+) (\w+) from the pantry$/ do |count, fruit|
+  @pantry.remove(fruit, count.to_i)
+end
+
+Then /^I should have (\d+) (\w+)$/ do |count, fruit|
+  @eattingMachine.fruit_total.should == count.to_i
+end
+
+Then /^I should have (\d+) (\w+) in my belly$/ do |count, fruit|
+  @eattingMachine.belly_count.should == count.to_i
+end
+
+Then /^I should have (\d+) (\w+) in the pantry$/ do |count, fruit|
+  @pantry.count(fruit).should == count.to_i
+end
+
+Then /^my shopping list should equal$/ do |list|
+  @shopping_list.should == list
+end

data/examples/tickets/features/step_definitons/tickets_steps.rb

@@ -0,0 +1,66 @@
+require 'spec/expectations'
+
+Given "be_empty" do
+  [1,2].should_not be_empty
+end
+
+Given "nested step is called" do
+  Given "I like mushroom", Cucumber::Ast::Table.new([
+    %w{sponge bob},
+    %w{is cool}
+  ])
+end
+
+Given 'nested step is called using text table' do
+  Given "I like mushroom", table(%{
+    | sponge | bob  |
+    | is     | cool |
+  })
+
+  # Alternative syntax (file and line will be reported on parse error)
+  # Given "I like mushroom", table(<<-EOT, __FILE__, __LINE__)
+  #   | sponge | bob  |
+  #   | is     | cool
+  # EOT
+end
+
+Given "I like $what" do |what, table|
+  @magic = what
+  @tool  = table.raw[0][0]
+end
+
+Then "nested step should be executed" do
+  @magic.should == 'mushroom'
+  @tool.should == 'sponge'
+end
+
+Given /^the following table$/ do |table|
+  @table = table
+end
+
+Then /^I should be (\w+) in (\w+)$/ do |key, value|
+  hash = @table.hashes[0]
+  hash[key].should == value
+end
+
+Then /^I should see a multiline string like$/ do |s|
+  s.should == %{A string
+that spans
+several lines}
+end
+
+Given /^the following users exist in the system$/ do |table|
+  table.hashes[0][:role_assignments].should == 'HUMAN RESOURCE'
+end
+
+Given /^I have a pending step$/ do
+  pending
+end
+
+When /^I run this feature with the progress format$/ do
+  pending
+end
+
+Then /^I should get a no method error for 'backtrace_line'$/ do
+  pending
+end

data/examples/tickets/features/tickets.feature

@@ -0,0 +1,28 @@
+Feature: Cucumber
+  In order to have a happy user base
+  As a Cucumber user
+  I don't want no stinkin bugs
+
+  Scenario: RSpec be_*
+    Given be_empty
+    
+  Scenario: Call step from step
+    Given nested step is called
+    Then nested step should be executed
+
+  Scenario: Call step from step using text table
+    Given nested step is called using text table
+    Then nested step should be executed
+    
+  Scenario: Reading a table
+    Given the following table
+      | born  | working |
+      | Oslo  | London  |
+    Then I should be working in London
+    And I should be born in Oslo
+    And I should see a multiline string like
+      """
+      A string
+      that spans
+      several lines
+      """

data/examples/watir/README.textile

@@ -0,0 +1,16 @@
+Here you'll find examples for Watir, FireWatir, SafariWatir and Celerity.
+All of these browser libraries have the same API, so the example code will
+work with all of them.
+
+Just run with:
+
+  rake features
+  
+This will use Watir/IE if you're on Windows, and SafariWatir/Safari if you're on OS X.
+You can force the use of FireWatir/Firefox on any platform like this:
+
+  rake features FIREWATIR=true
+  
+And finally, you can use Celerity by running in JRuby:
+
+  jruby -S rake features

data/examples/watir/Rakefile

@@ -0,0 +1,6 @@
+$:.unshift(File.dirname(__FILE__) + '/../../lib')
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new do |t|
+  t.cucumber_opts = %w{--format pretty}
+end

data/examples/watir/features/search.feature

@@ -0,0 +1,12 @@
+Feature: Search
+  In order to learn more
+  As an information seeker
+  I want to find more information
+
+  Scenario: Find what I'm looking for
+    Given I am on the Google search page
+    When I search for "cucumber github"
+    Then I should see
+      """
+      BDD that talks to domain experts first and code second
+      """

data/examples/watir/features/step_definitons/search_steps.rb

@@ -0,0 +1,22 @@
+# Full Watir API: http://wtr.rubyforge.org/rdoc/
+# Full RSpec API: http://rspec.rubyforge.org/
+
+Given 'I am on the Google search page' do
+  @browser.goto 'http://www.google.com/'
+end
+
+When /I search for "(.*)"/ do |query|
+  @browser.text_field(:name, 'q').set(query)
+  @browser.button(:name, 'btnG').click
+end
+
+Then /I should see/ do |text|
+  @browser.text.should =~ /#{text}/m
+end
+
+# To avoid step definitions that are tightly coupled to your user interface,
+# consider creating classes for your pages - such as this:
+# http://github.com/aslakhellesoy/cucumber/tree/v0.1.15/examples/watir/features/step_definitons/search_steps.rb
+#
+# You may keep the page classes along your steps, or even better, put them in separate files, e.g.
+# support/pages/google_search.rb

data/examples/watir/features/support/env.rb

@@ -0,0 +1,32 @@
+require 'spec/expectations'
+
+if ENV['FIREWATIR']
+  require 'firewatir'
+  Browser = FireWatir::Firefox
+else
+  case RUBY_PLATFORM
+  when /darwin/
+    require 'safariwatir'
+    Browser = Watir::Safari
+  when /win32|mingw/
+    require 'watir'
+    Browser = Watir::IE
+  when /java/
+    require 'celerity'
+    Browser = Celerity::Browser
+  else
+    raise "This platform is not supported (#{PLATFORM})"
+  end
+end
+
+# "before all"
+browser = Browser.new
+
+Before do
+  @browser = browser
+end
+
+# "after all"
+at_exit do
+  browser.close
+end

data/features/after_block_exceptions.feature

@@ -0,0 +1,102 @@
+Feature: After Block Exceptions
+  In order to use custom assertions at the end of each scenario
+  As a developer
+  I want exceptions raised in After blocks to be handled gracefully and reported by the formatters
+  
+  Background:
+    Given a standard Cucumber project directory structure
+    And a file named "features/step_definitions/steps.rb" with:
+      """
+      Given /^this step does something naughty$/ do
+        @naughty = true
+      end
+
+      Given /^this step works$/ do        
+      end
+      """
+    And a file named "features/support/env.rb" with:
+      """
+      class NaughtyScenarioException < Exception; end
+      After do
+        if @naughty
+          raise NaughtyScenarioException.new("This scenario has been very very naughty")
+        end
+      end
+      """
+
+  @mri186
+  Scenario: Handle Exception in standard scenario step and carry on
+    Given a file named "features/naughty_step_in_scenario.feature" with:
+      """
+      Feature: Sample
+
+        Scenario: Naughty Step
+          Given this step does something naughty
+
+        Scenario: Success
+          Given this step works
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+      
+        Scenario: Naughty Step                   # features/naughty_step_in_scenario.feature:3
+          Given this step does something naughty # features/step_definitions/steps.rb:1
+            This scenario has been very very naughty (NaughtyScenarioException)
+            ./features/support/env.rb:4:in `After'
+
+        Scenario: Success       # features/naughty_step_in_scenario.feature:6
+          Given this step works # features/step_definitions/steps.rb:5
+      
+      Failing Scenarios:
+      cucumber features/naughty_step_in_scenario.feature:3 # Scenario: Naughty Step
+      
+      2 scenarios (1 failed, 1 passed)
+      2 steps (2 passed)
+      
+      """
+
+  @mri186
+  Scenario: Handle Exception in scenario outline table row and carry on
+    Given a file named "features/naughty_step_in_scenario_outline.feature" with:
+      """
+      Feature: Sample
+
+        Scenario Outline: Naughty Step
+          Given this step <Might Work>
+          
+          Examples:
+          | Might Work             |
+          | works                  |
+          | does something naughty |
+          | works                  |
+
+        Scenario: Success
+          Given this step works
+          
+      """
+    When I run cucumber features
+    Then it should fail with 
+      """
+      Feature: Sample
+      
+        Scenario Outline: Naughty Step # features/naughty_step_in_scenario_outline.feature:3
+          Given this step <Might Work> # features/step_definitions/steps.rb:5
+      
+          Examples: 
+            | Might Work             |
+            | works                  |
+            | does something naughty |
+            This scenario has been very very naughty (NaughtyScenarioException)
+            ./features/support/env.rb:4:in `After'
+            | works                  |
+      
+        Scenario: Success       # features/naughty_step_in_scenario_outline.feature:12
+          Given this step works # features/step_definitions/steps.rb:5
+      
+      4 scenarios (1 failed, 3 passed)
+      4 steps (4 passed)
+      
+      """
+