kosmas58-cucumber 0.1.99.22 → 0.1.99.23

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,60 @@
+require 'spec/expectations'
+
+World do
+  Object.new
+end
+
+After do |scenario|
+  if scenario.status.index(:failed)
+    # Call the BDD police
+  end
+end
+
+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 shoule see a multiline string like$/ do |s|
+  s.should == %{A string
+that spans
+several lines}
+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 shoule 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 = "--format pretty"
+end

data/examples/watir/features/search.feature

@@ -0,0 +1,9 @@
+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 a link to "Ruby on Rails — cucumber — GitHub":http://github.com/aslakhellesoy/cucumber/wikis/ruby-on-rails

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

@@ -0,0 +1,24 @@
+# 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 a link to "(.*)":(.*)/ do |text, url|
+  link = @browser.link(:url, url)
+  link.should_not == nil
+  link.text.should == text
+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/background.feature

@@ -0,0 +1,223 @@
+Feature: backgrounds
+  In order to provide a context to my scenarios within a feature
+  As a feature editor
+  I want to write a background section in my features.
+
+  Scenario: run a specific scenario with a background
+    When I run cucumber -q features/background/passing_background.feature:9 --require features
+    Then it should pass with
+    """
+    Feature: Passing background sample
+    
+      Background: 
+        Given '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    1 scenario
+    2 passed steps
+    
+    """
+  
+  Scenario: run a feature with a background that passes
+    When I run cucumber -q features/background/passing_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Passing background sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario: passing background
+        Then I should have '10' cukes
+
+      Scenario: another passing background
+        Then I should have '10' cukes
+
+    2 scenarios
+    4 passed steps
+    
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that passes
+    When I run cucumber -q features/background/scenario_outline_passing_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Passing background with scenario outlines sample
+
+      Background: 
+        Given '10' cukes
+
+      Scenario Outline: passing background
+        Then I should have '<count>' cukes
+
+      Examples: 
+        | count |
+        | 10    |
+
+      Scenario Outline: another passing background
+        Then I should have '<count>' cukes
+
+      Examples: 
+        | count |
+        | 10    |
+
+    2 scenarios
+    4 passed steps
+
+    """
+
+  Scenario: run a feature with a background that fails
+    When I run cucumber -q features/background/failing_background.feature --require features
+    Then it should fail with
+    """
+    Feature: Failing background sample
+
+      Background: 
+        Given failing without a table
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/failing_background.feature:4:in `Given failing without a table'
+
+      Scenario: failing background
+        Then I should have '10' cukes
+
+      Scenario: another failing background
+        Then I should have '10' cukes
+
+    2 scenarios
+    2 failed steps
+    2 skipped steps
+
+    """
+
+  Scenario: run a feature with scenario outlines that has a background that fails
+    When I run cucumber -q features/background/scenario_outline_failing_background.feature --require features
+    Then it should fail with
+    """
+    Feature: Failing background with scenario outlines sample
+
+      Background: 
+        Given failing without a table
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
+          features/background/scenario_outline_failing_background.feature:4:in `Given failing without a table'
+
+      Scenario Outline: failing background
+        Then I should have '<count>' cukes
+
+      Examples: 
+        | count |
+        | 10    |
+
+      Scenario Outline: another failing background
+        Then I should have '<count>' cukes
+
+      Examples: 
+        | count |
+        | 10    |
+
+    2 scenarios
+    2 failed steps
+    2 skipped steps
+
+    """
+
+  Scenario: run a feature with a background that is pending
+    When I run cucumber -q features/background/pending_background.feature --require features
+    Then it should pass with
+    """
+    Feature: Pending background sample
+
+      Background: 
+        Given pending
+
+      Scenario: pending background
+        Then I should have '10' cukes
+
+      Scenario: another pending background
+        Then I should have '10' cukes
+
+    2 scenarios
+    2 skipped steps
+    2 undefined steps
+
+    """
+
+  Scenario: background passes with first scenario but fails with second
+    When I run cucumber -q features/background/failing_background_after_success.feature --require features
+    Then it should fail with
+    """
+    Feature: Failing background after previously successful background sample
+
+      Background: 
+        Given passing without a table
+        And '10' global cukes
+
+      Scenario: passing background
+        Then I should have '10' global cukes
+
+      Background: 
+        Given passing without a table
+        And '10' global cukes
+          FAIL (RuntimeError)
+          ./features/step_definitions/sample_steps.rb:2:in `flunker'
+          ./features/step_definitions/sample_steps.rb:37:in `/^'(.+)' global cukes$/'
+          features/background/failing_background_after_success.feature:3:in `And '10' global cukes'
+
+      Scenario: failing background
+        Then I should have '10' global cukes
+
+    2 scenarios
+    1 failed step
+    1 skipped step
+    4 passed steps
+
+    """
+
+  Scenario: background with multline args
+  When I run cucumber -q features/background/multiline_args_background.feature --require features
+  Then it should pass with
+    """
+    Feature: Passing background with multiline args
+
+      Background: 
+        Given table
+          | a | b |
+          | c | d |
+        And multiline string
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+      Scenario: passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+      Scenario: another passing background
+        Then the table should be
+          | a | b |
+          | c | d |
+        Then the multiline string should be
+          \"\"\"
+            I'm a cucumber and I'm okay. 
+            I sleep all night and I test all day
+          \"\"\"
+
+    2 scenarios
+    8 passed steps
+    
+    """
+
+  #@josephwilk
+  Scenario: run a scenario showing explicit background steps --explicit-background