stefl-cucumber 0.10.1

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

@@ -0,0 +1,28 @@
+# 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/fixtures/tickets/features/177/2.feature

@@ -0,0 +1,20 @@
+# 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/fixtures/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/fixtures/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/fixtures/tickets/features/229/tagged_hooks.feature

@@ -0,0 +1,8 @@
+Feature: Tagged hooks
+  In order to provide more flexible setups
+  I should be able to specify exactly
+  where hooks are executed
+  
+  @i_am_so_special
+  Scenario: Yes I am
+    When special me goes to town

data/fixtures/tickets/features/229/tagged_hooks.rb

@@ -0,0 +1,14 @@
+begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
+
+Before('@i_am_so_special') do
+  @something_special = 10
+end
+
+After('@i_am_so_special') do
+  @something_special.should == 20
+end
+
+When /special me goes to town/ do
+  @something_special.should == 10
+  @something_special = 20
+end

data/fixtures/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/fixtures/tickets/features/241.feature

@@ -0,0 +1,12 @@
+# 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/fixtures/tickets/features/246.feature

@@ -0,0 +1,4 @@
+Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/246-distorted-console-output-for-slightly-complicated-step-regexp-match
+
+Scenario: See "No Record(s) Found" for Zero Existing
+   Given no public holiday exists in the system

data/fixtures/tickets/features/248.feature

@@ -0,0 +1,11 @@
+Feature: pending method causes failure in Scenario Outlines 
+
+  Scenario Outline: blah
+    Given this is pending until we fix it
+    Given context with <Stuff>
+    When action
+    Then outcome with <Blah>
+
+  Examples:
+    | Stuff  | Blah        |
+    | Cheese | Pepper Jack |

data/fixtures/tickets/features/270/back.feature

@@ -0,0 +1,14 @@
+Feature: Background
+  In for background to work properly
+  As a user
+  I want it to run transactionally and only once when I call an individual scenario
+  
+Background:
+  Given plop
+ 
+Scenario: Barping
+  When I barp
+ 
+ 
+Scenario: Wibbling
+  When I wibble

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

@@ -0,0 +1,14 @@
+begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
+
+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/fixtures/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/fixtures/tickets/features/272/hooks_steps.rb

@@ -0,0 +1,53 @@
+begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
+
+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/fixtures/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/fixtures/tickets/features/279/py_string_indent.steps.rb

@@ -0,0 +1,12 @@
+begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
+
+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/fixtures/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/fixtures/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/fixtures/tickets/features/301/filter_background_tagged_hooks_steps.rb

@@ -0,0 +1,12 @@
+begin require 'rspec/expectations'; rescue LoadError; require 'spec/expectations'; end
+
+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/fixtures/tickets/features/306/only_background.feature

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

data/fixtures/tickets/features/around_timeout.feature

@@ -0,0 +1,6 @@
+Feature: Be fast
+
+  @fast
+  Scenario: Fail if too slow
+    # This will start failing if we change the number above 0.5
+    When I take 0.2 seconds to complete

data/fixtures/tickets/features/gherkin_67.feature

@@ -0,0 +1,12 @@
+Feature:
+  @wip
+  Scenario Outline:
+    When blah
+
+    Examples:
+      | a |
+      | b |
+      | c |
+
+  Scenario:
+    When blah

data/fixtures/tickets/features/gherkin_68.feature

@@ -0,0 +1,4 @@
+Feature:
+  Scenario:
+    Given I call empty steps
+  

data/fixtures/tickets/features/half_manual.feature

@@ -0,0 +1,11 @@
+@ask
+Feature: Half manual
+  In order to speed up manual tests
+  Testers should at least be able to automate parts of it
+  
+  Scenario: Check mailbox
+    Given I have signed up on the web
+    When I check my mailbox
+    Then I should have an email containing "cukes"
+
+  

data/fixtures/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/fixtures/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/fixtures/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   |