kosmas58-cucumber 0.1.99.21 → 0.1.99.22

data/examples/self_test/features/lots_of_undefined.feature

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

data/examples/self_test/features/outline_sample.feature

@@ -1,15 +0,0 @@
-Feature: Outline Sample
-
-  Scenario: I have no steps
-
-  Scenario Outline: Test state
-    Given <state> without a table
-    Given <other_state> without a table
-  Examples: Rainbow colours
-    |  state   | other_state |
-    | missing |  passing|
-    | passing| passing |
-| failing | passing |
-Examples:Only passing
-|  state   | other_state |
-| passing  | passing |

data/examples/self_test/features/sample.feature

@@ -1,19 +0,0 @@
-@one
-Feature: Sample
-
-    @two @three
-  Scenario: Missing
-    Given missing
-
-@three
-  Scenario: Passing
-    Given passing
-      |a|b|
-      |c|d|
-  
-  @four
-  Scenario: Failing
-    Given failing
-      """
-      hello
-      """

data/examples/self_test/features/step_definitions/sample_steps.rb

@@ -1,62 +0,0 @@
-def flunker
-  raise "FAIL"
-end
-
-Given /^passing$/ do |table|
-end
-
-Given /^failing$/ do |string|
-  flunker
-end
-
-Given /^passing without a table$/ do
-end
-
-Given /^failing without a table$/ do
-  flunker
-end
-
-Given /^a step definition that calls an undefined step$/ do
-  Given 'this does not exist'
-end
-
-Given /^call step "(.*)"$/ do |step|
-  Given step
-end
-
-Given /^'(.+)' cukes$/ do |cukes|
-  @cukes = cukes
-end
-
-Then /^I should have '(.+)' cukes$/ do |cukes|
-  @cukes.should == cukes
-end
-
-Given /^'(.+)' global cukes$/ do |cukes|
-  $scenario_runs ||= 0
-  flunker if $scenario_runs > 0
-  $cukes = cukes
-  $scenario_runs += 1
-end
-
-Then /^I should have '(.+)' global cukes$/ do |cukes|
-  $cukes.should == cukes
-end
-
-Given /^table$/ do |table|
-  @table = table
-end
-
-Given /^multiline string$/ do |string|
-  @multiline = string
-end
-
-Then /^the table should be$/ do |table|
-  @table.to_sexp.should == table.to_sexp
-end
-
-Then /^the multiline string should be$/ do |string|
-  @multiline.should == string
-end
-
-

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

@@ -1 +0,0 @@
-require 'spec/expectations'

data/examples/self_test/features/support/tag_count_formatter.rb

@@ -1,25 +0,0 @@
-module Tag
-  # Custom formatter that reports occurrences of each tag
-  class Count < Cucumber::Ast::Visitor
-    def initialize(step_mother, io, options)
-      super(step_mother)
-      @io = io
-      @counts = Hash.new{|h,k| h[k] = 0}
-    end
-
-    def visit_features(features)
-      super
-      print_summary
-    end
-
-    def visit_tag_name(tag_name)
-      @counts[tag_name] += 1
-    end
-    
-    def print_summary
-      matrix = @counts.to_a.sort{|paira, pairb| paira[0] <=> pairb[0]}.transpose
-      table = Cucumber::Ast::Table.new(matrix)
-      Cucumber::Formatter::Pretty.new(@step_mother, @io, {}).visit_multiline_arg(table, :tag)
-    end
-  end
-end

data/examples/test_unit/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/test_unit/features/step_definitions/test_unit_steps.rb

@@ -1,26 +0,0 @@
-require 'test/unit/assertions'
-World do |o|
-  o.extend(Test::Unit::Assertions)
-  o
-end
-
-Given /^(\w+) = (\w+)$/ do |var, value|
-  instance_variable_set("@#{var}", value)
-end
-
-begin
-  require 'rubygems'
-  require 'matchy'
-  Then /^I can assert that (\w+) == (\w+)$/ do |var_a, var_b|
-    a = instance_variable_get("@#{var_a}")
-    b = instance_variable_get("@#{var_b}")
-    a.should == b
-  end
-rescue LoadError
-  STDERR.puts "***** You should install matchy *****"
-  Then /^I can assert that (\w+) == (\w+)$/ do |var_a, var_b|
-    a = instance_variable_get("@#{var_a}")
-    b = instance_variable_get("@#{var_b}")
-    assert_equal(a, b)
-  end
-end

data/examples/test_unit/features/test_unit.feature

@@ -1,9 +0,0 @@
-Feature: Test::Unit
-  In order to please people who like Test::Unit
-  As a Cucumber user
-  I want to be able to use assert* in my step definitions
-
-  Scenario: assert_equal
-    Given x = 5
-    And y = 5
-    Then I can assert that x == y

data/examples/tickets/Rakefile

@@ -1,11 +0,0 @@
-$:.unshift(File.dirname(__FILE__) + '/../../lib')
-require 'cucumber/rake/task'
-
-# Try these:
-#
-# rake features
-# rake features PROFILE=html
-Cucumber::Rake::Task.new do |t|
-  profile = ENV['PROFILE'] || 'default'
-  t.cucumber_opts = "--profile #{profile}"
-end

data/examples/tickets/cucumber.yml

@@ -1,2 +0,0 @@
-default: --format pretty
-html: --format html --out features.html

data/examples/tickets/features/172.feature

@@ -1,28 +0,0 @@
-Feature: Login
-  To ensure the safety of the application
-  A regular user of the system
-  Must authenticate before using the app
-
-
-  Scenario Outline: Failed Login
-    Given the user "known_user"
-
-    When I go to the main page
-    Then I should see the login form
-
-    When I fill in "login" with "<login>"
-    And I fill in "password" with "<password>"
-    And I press "Log In"
-    Then the login request should fail
-    And I should see the error message "Login or Password incorrect"
-
-    Examples:
-      | login        | password       |
-      |              |                |
-      | unknown_user |                |
-      | known_user   |                |
-      |              | wrong_password |
-      |              | known_userpass |
-      | unknown_user | wrong_password |
-      | unknown_user | known_userpass |
-      | known_user   | wrong_password |

data/examples/tickets/features/177/1.feature

@@ -1,29 +0,0 @@
-Users want to know that nobody can masquerade as them.  We want to extend trust
-only to visitors who present the appropriate credentials.  Everyone wants this
-identity verification to be as secure and convenient as possible.
-
-Feature: Logging in
-  As an anonymous user with an account
-  I want to log in to my account
-  So that I can be myself
-
-  #
-  # Log in: get form
-  #
-  Scenario: Anonymous user can get a login form.
-    Given I am logged out
-    When  I go to "/login"
-    Then  I should be at the "sessions/new" page
-
-  #
-  # Log in successfully, but don't remember me
-  #
-  Scenario: Anonymous user can log in
-    Given an "activated" user named "reggie" exists
-     And  I am logged out
-    When  I go to "/login"
-     And  I fill in "Login" with "reggie"
-     And  I fill in "Password" with "password"
-     And  I press "Log in"
-    Then  I should be at the "dashboard/index" page
-

data/examples/tickets/features/177/2.feature

@@ -1,21 +0,0 @@
-Visitors may create an account, but for those who are not already in the 
-system an someone must activate the account for them before it can be used.
-
-Feature: Activating an account
-  As a registered, but not yet activated, user
-  I want to be able to activate my account
-  So that I can log in to the site
-  
-  Scenario: Not-yet-activated user can activate her account
-    Given a registered user named 'Reggie' # need to rewrite
-  #    And  the user has activation_code: 'activate_me', activated_at: nil! 
-  #    And  we try hard to remember the user's updated_at, and created_at
-  #   When  she goes to /activate/activate_me
-  #   Then  she should be redirected to 'login'
-  #   When  she follows that redirect!
-  #   Then  she should see a notice message 'Signup complete!'
-  #    And  a user with login: 'reggie' should exist
-  #    And  the user should have login: 'reggie', and email: 'registered@example.com'
-  #    And  the user's activation_code should     be nil
-  #    And  the user's activated_at    should not be nil
-  #    And  she should not be logged in

data/examples/tickets/features/177/3.feature

@@ -1,18 +0,0 @@
-Feature: Matt's example with a comment before a step
-
-Scenario: Upload an image for an artist and create a concert in the process
-  Given I am logged in to my account
-  And there is one Artist named "Pixies"
-  And there is one Venue
-  When I visit the page for the Artist
-  And I follow "add a photo"
-  And I upload an Image
-  # Search on select concert page
-  And I press "Search Pixies concerts" 
-  And I follow "Add a new Concert"
-  And I fill in new Concert information
-  And I press "Preview"
-  And I press "Add concert"
-  # No artists appear in this photo
-  And I press "Submit" 
-  Then my Concert should exist with 1 Image

data/examples/tickets/features/180.feature

@@ -1,7 +0,0 @@
-Feature: Cucumber command line
-  In order to write better software
-  Developers should be able to execute requirements as tests
-
-  
-  Scenario: Pending Scenario at the end of a file with whitespace after it
-  

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

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

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

@@ -1,95 +0,0 @@
-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/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,60 +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
-  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