aslakhellesoy-cucumber 0.1.99.3 → 0.1.99.4

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

@@ -1,42 +0,0 @@
-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

@@ -1,61 +0,0 @@
-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
-  pending
-  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

@@ -1,28 +0,0 @@
-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

@@ -1,16 +0,0 @@
-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

@@ -1,6 +0,0 @@
-$:.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

@@ -1,9 +0,0 @@
-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

@@ -1,24 +0,0 @@
-# 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

@@ -1,32 +0,0 @@
-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/cucumber_cli.feature

@@ -1,327 +0,0 @@
-Feature: Cucumber command line
-  In order to write better software
-  Developers should be able to execute requirements as tests
-
-  Scenario: Run single scenario with missing step definition
-    When I run cucumber -q features/sample.feature:5
-    Then it should pass with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-      1 scenario
-      1 undefined step
-
-      """
-
-  Scenario: Fail with --strict
-    When I run cucumber -q features/sample.feature:5 --strict
-    Then it should fail with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-            Undefined step: "missing" (Cucumber::StepMother::Undefined)
-            features/sample.feature:6:in `Given missing'
-
-      1 scenario
-      1 failed step
-
-      """
-
-  Scenario: Specify 2 line numbers where one is a tag
-    When I run cucumber -q features/sample.feature:5:14
-    Then it should fail with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @four
-        Scenario: Failing
-          Given failing
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-            features/sample.feature:16:in `Given failing'
-
-      2 scenarios
-      1 failed step
-      1 undefined step
-
-      """
-
-  Scenario: Require missing step definition from elsewhere
-    When I run cucumber -q -r ../../features/step_definitions/extra_steps.rb features/sample.feature:5
-    Then it should pass with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-      1 scenario
-      1 passed step
-
-      """
-
-  Scenario: Specify the line number of a row
-    When I run cucumber -q features/sample.feature:12
-    Then it should pass with
-      """
-      @one
-      Feature: Sample
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      1 scenario
-      1 passed step
-
-      """
-
-  Scenario: Run all with progress formatter
-    When I run cucumber -q --format progress features/sample.feature
-    Then it should fail with
-      """
-      U.F
-
-      (::) failed steps (::)
-
-      FAIL (RuntimeError)
-      ./features/step_definitions/sample_steps.rb:2:in `flunker'
-      ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-      features/sample.feature:16:in `Given failing'
-
-      3 scenarios
-      1 failed step
-      1 undefined step
-      1 passed step
-
-      """
-
-  Scenario: Run Norwegian
-    Given I am in i18n/no
-    When I run cucumber -q --language no features
-    Then it should pass with
-      """
-      Egenskap: Summering
-        For å slippe å gjøre dumme feil
-        Som en regnskapsfører
-        Vil jeg kunne legge sammen
-
-        Scenario: to tall
-          Gitt at jeg har tastet inn 5
-          Og at jeg har tastet inn 7
-          Når jeg summerer
-          Så skal resultatet være 12
-
-        @iterasjon3
-        Scenario: tre tall
-          Gitt at jeg har tastet inn 5
-          Og at jeg har tastet inn 7
-          Og at jeg har tastet inn 1
-          Når jeg summerer
-          Så skal resultatet være 13
-
-      2 scenarios
-      9 passed steps
-
-      """
-
-  Scenario: --dry-run
-    When I run cucumber --dry-run --no-snippets features
-    Then it should pass with
-      """
-      Feature: Calling undefined step
-
-        Scenario: Call directly
-          Given a step definition that calls an undefined step
-
-        Scenario: Call via another
-          Given call step "a step definition that calls an undefined step"
-
-      Feature: Lots of undefined
-
-        Scenario: Implement me
-          Given it snows in Sahara
-          Given it's 40 degrees in Norway
-          And it's 40 degrees in Norway
-          When I stop procrastinating
-          And there is world peace
-
-      Feature: Outline Sample
-
-        Scenario: I have no steps
-
-        Scenario Outline: Test state
-          Given <state> without a table
-          Given <other_state> without a table
-
-        Examples: 
-          | state   | other_state |
-          | missing | passing     |
-          | passing | passing     |
-          | failing | passing     |
-
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-
-      10 scenarios
-      9 skipped steps
-      7 undefined steps
-
-      """
-
-  Scenario: Multiple formatters and outputs
-    When I run cucumber --format progress --out tmp/progress.txt --format pretty --out tmp/pretty.txt  --dry-run features/lots_of_undefined.feature
-    And examples/self_test/tmp/progress.txt should contain
-      """
-      UUUUU
-
-      1 scenario
-      5 undefined steps
-
-      """
-    And examples/self_test/tmp/pretty.txt should match
-      """
-      Feature: Lots of undefined
-
-        Scenario: Implement me
-          Given it snows in Sahara
-          Given it's 40 degrees in Norway
-          And it's 40 degrees in Norway
-          When I stop procrastinating
-          And there is world peace
-
-      1 scenario
-      5 undefined steps
-
-      """
-
-  Scenario: Run scenario specified by name using --scenario
-    When I run cucumber --scenario Passing -q features
-    Then it should pass with
-      """
-      @one
-      Feature: Sample
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      1 scenario
-      1 passed step
-
-      """
-
-  Scenario: Run with a tag that exists on 2 scenarios
-    When I run cucumber -q features --tags three
-    Then it should pass with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-      2 scenarios
-      1 undefined step
-      1 passed step
-
-      """
-
-  Scenario: Run with a tag that exists on 1 feature
-    When I run cucumber -q features --tags one
-    Then it should fail with
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:9:in `/^failing$/'
-            features/sample.feature:16:in `Given failing'
-
-      3 scenarios
-      1 failed step
-      1 undefined step
-      1 passed step
-
-      """
-
-  Scenario: Reformat files with --autoformat
-    When I run cucumber --autoformat tmp/formatted features
-    Then examples/self_test/tmp/formatted/features/sample.feature should contain
-      """
-      @one
-      Feature: Sample
-
-        @two @three
-        Scenario: Missing
-          Given missing
-
-        @three
-        Scenario: Passing
-          Given passing
-            | a | b |
-            | c | d |
-
-        @four
-        Scenario: Failing
-          Given failing
-
-
-      """
-

data/features/cucumber_cli_outlines.feature

@@ -1,81 +0,0 @@
-Feature: Cucumber command line
-  In order to write better software
-  Developers should be able to execute requirements as tests
-
-  Scenario: Run scenario outline steps only
-    When I run cucumber -q features/outline_sample.feature:7
-    Then it should fail with
-      """
-      Feature: Outline Sample
-
-        Scenario Outline: Test state
-          Given <state> without a table
-          Given <other_state> without a table
-
-        Examples: 
-          | state   | other_state |
-          | missing | passing     |
-          | passing | passing     |
-          | failing | passing     |
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
-            features/outline_sample.feature:12:in `Given failing without a table'
-
-      3 scenarios
-      1 failed step
-      2 skipped steps
-      1 undefined step
-      2 passed steps
-
-      """
-
-  Scenario: Run single failing scenario outline table row
-    When I run cucumber features/outline_sample.feature:12
-    Then it should fail with
-      """
-      Feature: Outline Sample
-
-        Scenario Outline: Test state          # features/outline_sample.feature:5
-          Given <state> without a table
-          Given <other_state> without a table
-
-        Examples: 
-          | state   | other_state |
-          | failing | passing     |
-            FAIL (RuntimeError)
-            ./features/step_definitions/sample_steps.rb:2:in `flunker'
-            ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
-            features/outline_sample.feature:12:in `Given failing without a table'
-
-      1 scenario
-      1 failed step
-      1 skipped step
-
-      """
-
-  Scenario: Run all with progress formatter
-    When I run cucumber -q --format progress features/outline_sample.feature
-    Then it should fail with
-      """
-      UUS..FS
-
-      (::) undefined scenarios (::)
-
-      features/outline_sample.feature:3:in `Scenario: I have no steps'
-
-      (::) failed steps (::)
-
-      FAIL (RuntimeError)
-      ./features/step_definitions/sample_steps.rb:2:in `flunker'
-      ./features/step_definitions/sample_steps.rb:16:in `/^failing without a table$/'
-      features/outline_sample.feature:12:in `Given failing without a table'
-
-      4 scenarios
-      1 failed step
-      2 skipped steps
-      1 undefined step
-      2 passed steps
-
-      """
-

data/features/report_called_undefined_steps.feature

@@ -1,32 +0,0 @@
-Feature: Cucumber command line
-  In order to find out what step definitions need to be implemented
-  Developers should always see what step definition is missing
-
-  Scenario: Get info at arbitrary levels of nesting
-    When I run cucumber features/call_undefined_step_from_step_def.feature
-    Then it should pass with
-      """
-      Feature: Calling undefined step
-
-        Scenario: Call directly                                # features/call_undefined_step_from_step_def.feature:3
-          Given a step definition that calls an undefined step # features/step_definitions/sample_steps.rb:19
-            Undefined step: "this does not exist" (Cucumber::StepMother::Undefined)
-            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
-
-        Scenario: Call via another                                         # features/call_undefined_step_from_step_def.feature:6
-          Given call step "a step definition that calls an undefined step" # features/step_definitions/sample_steps.rb:23
-            Undefined step: "this does not exist" (Cucumber::StepMother::Undefined)
-            ./features/step_definitions/sample_steps.rb:20:in `/^a step definition that calls an undefined step$/'
-
-      2 scenarios
-      2 undefined steps
-
-      You can implement step definitions for missing steps with these snippets:
-
-      Given /^this does not exist$/ do
-        pending
-      end
-
-
-      """
-

data/features/step_definitions/cucumber_steps.rb

@@ -1,31 +0,0 @@
-Given /^I am in (.*)$/ do |dir|
-  @dir = dir
-end
-
-When /^I run cucumber (.*)$/ do |cmd|
-  @dir ||= 'self_test'
-  full_dir ||= File.expand_path(File.dirname(__FILE__) + "/../../examples/#{@dir}")
-  Dir.chdir(full_dir) do
-    @full_cmd = "#{Cucumber::RUBY_BINARY} #{Cucumber::BINARY} --no-color #{cmd}"
-    @out = `#{@full_cmd}`
-    @status = $?.exitstatus
-  end
-end
-
-Then /^it should (fail|pass) with$/ do |success, output|
-#puts @out
-  @out.should == output
-  if success == 'fail'
-    @status.should_not == 0
-  else
-    @status.should == 0
-  end
-end
-
-Then /^(.*) should contain$/ do |file, text|
-  IO.read(file).should == text
-end
-
-Then /^(.*) should match$/ do |file, text|
-  IO.read(file).should =~ Regexp.new(text)
-end

data/features/step_definitions/extra_steps.rb

@@ -1,2 +0,0 @@
-Given /^missing$/ do
-end