kosmas58-cucumber 0.1.16.6 → 0.1.99.21

data/examples/self_test/features/background/passing_background.feature

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

data/examples/self_test/features/background/pending_background.feature

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

data/examples/self_test/features/background/scenario_outline_failing_background.feature

@@ -0,0 +1,16 @@
+Feature: Failing background with scenario outlines sample
+
+  Background:
+    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  |

data/examples/self_test/features/background/scenario_outline_passing_background.feature

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

data/examples/self_test/features/call_undefined_step_from_step_def.feature

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

data/examples/self_test/features/lots_of_undefined.feature

@@ -0,0 +1,8 @@
+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,9 +1,15 @@
 Feature: Outline Sample
 
+  Scenario: I have no steps
+
   Scenario Outline: Test state
     Given <state> without a table
-    Examples:
-      |  state  |
-      | missing |
-      | passing |
-      | failing |
+    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,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,62 @@
+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 > 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

@@ -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, :tag)
+    end
+  end
+end

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/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,44 @@ 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 "nested step"
+  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 "nested step" do
-  @magic = 'mushroom'
+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|

data/examples/tickets/features/tickets.feature

@@ -9,6 +9,10 @@ Feature: Cucumber
   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

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