cucumber 0.1.16 → 0.2.0

data/examples/self_test/features/sample.feature

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

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

@@ -1,13 +1,64 @@
+def flunker
+  raise "FAIL"
+end
+
 Given /^passing$/ do |table|
 end
 
-Given /^failing$/ do |table|
-  raise "FAIL"
+Given /^failing$/ do |string|
+  flunker
 end
 
 Given /^passing without a table$/ do
 end
 
 Given /^failing without a table$/ do
-  raise "FAIL"
-end
+  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 >= 1
+  $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
+
+Given /^failing expectation$/ do
+  'this'.should == 'that'
+end

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

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

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

@@ -0,0 +1,25 @@
+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)
+    end
+  end
+end

data/examples/sinatra/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/sinatra/app.rb

@@ -0,0 +1,14 @@
+begin
+  require 'sinatra'
+rescue LoadError
+  require 'rubygems'
+  require 'sinatra'
+end
+
+get '/add' do
+  erb :add
+end
+
+post '/add' do
+  "Answer: #{params[:first].to_i + params[:second].to_i}"
+end

data/examples/sinatra/features/add.feature

@@ -0,0 +1,11 @@
+Feature: Addition
+  In order to avoid silly mistakes
+  As a math idiot 
+  I want to be told the sum of two numbers
+
+  Scenario: Add two numbers
+    Given I visit the calculator page
+    And I fill in '50' for 'first'
+    And I fill in '70' for 'second'
+    When I press 'Add'
+    Then I should see 'Answer: 120'

data/examples/sinatra/features/step_definitions/add_steps.rb

@@ -0,0 +1,15 @@
+Given /^I visit the calculator page$/ do
+  visit '/add'
+end
+
+Given /^I fill in '(.*)' for '(.*)'$/ do |value, field|
+  fill_in(field, :with => value)
+end
+
+When /^I press '(.*)'$/ do |name|
+  click_button(name)
+end
+
+Then /^I should see '(.*)'$/ do |text|
+  response.should contain(/#{text}/m)
+end

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

@@ -0,0 +1,20 @@
+# Sinatra
+require File.join(File.dirname(__FILE__), *%w[.. .. app])
+# Force the application name because polyglot breaks the auto-detection logic.
+Sinatra::Application.app_file = File.join(File.dirname(__FILE__), *%w[.. .. app.rb])
+
+# RSpec
+require 'spec/expectations'
+
+# Webrat
+require 'webrat'
+Webrat.configure do |config|
+  config.mode = :sinatra
+end
+
+World do
+  session = Webrat::SinatraSession.new
+  session.extend(Webrat::Matchers)
+  session.extend(Webrat::HaveTagMatcher)
+  session
+end

data/examples/sinatra/views/add.erb

@@ -0,0 +1,5 @@
+<form method='post' action='/add'>
+  <input name='first'/>
+  <input name='second'/>
+  <input type='submit' value='Add'/>
+</form>

data/examples/sinatra/views/layout.erb

@@ -0,0 +1,8 @@
+<html>
+  <head>
+    <title>Addition</title>
+  </head>
+  <body>
+    <%= yield %>
+  </body>
+</html>

data/examples/tickets/Rakefile

@@ -1,11 +1,16 @@
 $:.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
+Cucumber::Rake::Task.new(:pretty) do |t|
+  t.cucumber_opts = "--format pretty"
+end
+
+Cucumber::Rake::Task.new(:html) do |t|
+  t.cucumber_opts = "--format html --out features.html"
+end
+
+Cucumber::Rake::Task.new(:progress) do |t|
+  t.cucumber_opts = "--format progress -i -n"
+end
+
+task :default => [:pretty, :html, :progress]

data/examples/tickets/cucumber.yml

@@ -1,2 +1,3 @@
 default: --format pretty
-html: --format html --out features.html
+html: --format html --out features.html
+progress: --format progress -i -n

data/examples/tickets/features/172.feature

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

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

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

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

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

@@ -0,0 +1,13 @@
+Feature: Unsubstituted argument placeholder 
+
+  Scenario Outline: See Annual Leave Details (as Management & Human Resource)
+   Given the following users exist in the system
+     | name   | email           | role_assignments | group_memberships |
+     | Jane   | jane@fmail.com  | <role>           | Sales (manager)   |
+     | Max    | max@fmail.com   |                  | Sales (member)    |
+     | Carol  | carol@fmail.com |                  | Sales (member)    |
+     | Cat    | cat@fmail.com   |                  |                   |
+
+   Examples:
+     | role           |
+     | HUMAN RESOURCE |

data/examples/tickets/features/241.feature

@@ -0,0 +1,13 @@
+Users want to use cucumber, so tests are necessary to verify
+it is all working as expected
+
+Feature: Using the Console Formatter
+  In order to verify this error
+  I want to run this feature using the progress format
+  So that it can be fixed
+  
+  Scenario: A normal feature
+    Given I have a pending step
+    When  I run this feature with the progress format
+    Then  I should get a no method error for 'backtrace_line'
+

data/examples/tickets/features/scenario_outline.feature

@@ -19,10 +19,15 @@ Feature: Outlines
     Then I should have <left> cucumbers
     And I should have <eat> cucumbers in my belly
 
-  Examples:
+  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

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

@@ -4,20 +4,41 @@ World do
   Object.new
 end
 
+After do |scenario|
+end
+
 Given "be_empty" do
   [1,2].should_not be_empty
 end
 
 Given "nested step is called" do
-  Given "nested step"
+  Given "I like mushroom", Cucumber::Ast::Table.new([
+    %w{sponge bob},
+    %w{is cool}
+  ])
 end
 
-Given "nested step" do
-  @magic = 'mushroom'
+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|
@@ -29,8 +50,24 @@ Then /^I should be (\w+) in (\w+)$/ do |key, value|
   hash[key].should == value
 end
 
-Then /^I shoule see a multiline string like$/ do |s|
+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