square-cucumber 0.3.12.2 → 0.3.93.1

data/features/junit_formatter.feature

@@ -6,42 +6,49 @@ Feature: JUnit output formatter
     Given I am in junit
     And the tmp directory is empty
   
-  @mri186 @diffxml
+  @mri186
   Scenario: one feature, one passing scenario, one failing scenario
     When I run cucumber --format junit --out tmp/ features/one_passing_one_failing.feature
     Then it should fail with
       """
 
       """
-    And "examples/junit/tmp/TEST-one_passing_one_failing.xml" should contain XML
+    And "examples/junit/tmp/TEST-one_passing_one_failing.xml" with junit duration "0.005" should contain
       """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" tests="2" name="One passing scenario, one failing scenario" failures="1">
-      <testcase name="Given a passing scenario" classname="One passing scenario, one failing scenario.Passing">
+      <?xml encoding="UTF-8" version="1.0"?>
+      <testsuite errors="0" failures="1" name="One passing scenario, one failing scenario" tests="2" time="0.005">
+      <testcase classname="One passing scenario, one failing scenario.Passing" name="Passing" time="0.005">
       </testcase>
-      <testcase name="Given a failing scenario" classname="One passing scenario, one failing scenario.Failing">
-        <failure message="Given a failing scenario">
+      <testcase classname="One passing scenario, one failing scenario.Failing" name="Failing" time="0.005">
+        <failure message="failed Failing" type="failed">
+      Scenario: Failing
+
+      Given a failing scenario
+
+      Message:
        (RuntimeError)
       ./features/step_definitions/steps.rb:6:in `/a failing scenario/'
       features/one_passing_one_failing.feature:7:in `Given a failing scenario'  </failure>
       </testcase>
       </testsuite>
-      
+
       """
   
-  @mri186 @diffxml
+  @mri186
   Scenario: pending step
     When I run cucumber --format junit --out tmp/ features/pending.feature
     Then it should pass with
       """
       
       """
-    And "examples/junit/tmp/TEST-pending.xml" should contain XML
+    And "examples/junit/tmp/TEST-pending.xml" with junit duration "0.009" should contain
       """
-      <?xml version="1.0" encoding="UTF-8"?>
-      <testsuite errors="0" tests="1" name="Pending step" failures="1">
-      <testcase name="Given a pending step" classname="Pending step.Pending">
-        <failure message="Given a pending step">
+      <?xml encoding="UTF-8" version="1.0"?>
+      <testsuite errors="0" failures="1" name="Pending step" tests="1" time="0.009">
+      <testcase classname="Pending step.Pending" name="Pending" time="0.009">
+        <failure message="pending Pending" type="pending">
+      Scenario: Pending
+
       TODO (Cucumber::Pending)
       ./features/step_definitions/steps.rb:10:in `/a pending step/'
       features/pending.feature:4:in `Given a pending step'  </failure>

data/features/profiles.feature

@@ -0,0 +1,99 @@
+Feature: Profiles
+  In order to save time and prevent carpal tunnel syndrome
+  Cucumber users can save and reuse commonly used cucumber flags in a 'cucumber.yml' file.
+  These named arguments are called profiles and the yml file should be in the root of your project.
+  Any cucumber argument is valid in a profile.  To see all the available flags type 'cucumber --help'
+  For more information about profiles please see the wiki:
+  http://wiki.github.com/aslakhellesoy/cucumber/cucumberyml
+
+  Background: Basic App
+    Given a standard Cucumber project directory structure
+    And a file named "features/sample.feature" with:
+      """
+      Feature: Sample
+        Scenario: this is a test
+          Given I am just testing stuff
+      """
+    And a file named "features/support/env.rb"
+    And a file named "features/support/super_env.rb"
+    And the following profiles are defined:
+      """
+      default: features/sample.feature --require features/support/env.rb -v
+      super: features/sample.feature --require features/support/super_env.rb -v
+      """
+
+  Scenario: Explicitly defining a profile to run
+    When I run cucumber features/sample.feature --profile super
+    Then the output should contain
+      """
+      Using the super profile...
+      """
+    And exactly these files should be loaded: features/support/super_env.rb
+
+  Scenario: Defining multiple profiles to run
+    When I run cucumber features/sample.feature --profile default --profile super
+    Then the output should contain
+      """
+      Using the default and super profiles...
+      """
+    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
+
+  Scenario: Arguments passed in but no profile specified
+    When I run cucumber -v
+    Then the default profile should be used
+    And exactly these files should be loaded: features/support/env.rb
+
+  Scenario: Trying to use a missing profile
+    When I run cucumber -p foo
+    Then STDERR should be
+      """
+      Could not find profile: 'foo'
+
+      Defined profiles in cucumber.yml:
+        * default
+        * super
+
+      """
+
+  Scenario Outline: Disabling the default profile
+    When I run cucumber -v features/ <Flag>
+    Then the output should contain
+      """
+      Disabling profiles...
+      """
+    And exactly these files should be loaded: features/support/env.rb, features/support/super_env.rb
+
+    Examples:
+    |   Flag          |
+    | -P              |
+    | --no-profile    |
+
+
+  Scenario: Overriding the profile's features to run
+    Given a file named "features/another.feature" with:
+      """
+      Feature: Just this one should be ran
+      """
+      When I run cucumber -p default features/another.feature
+      Then exactly these features should be ran: features/another.feature
+
+  Scenario: Overriding the profile's formatter
+    You will most likely want to define a formatter in your default formatter.
+    However, you often want to run your features with a different formatter
+    yet still use the other the other arguments in the profile. Cucumber will
+    allow you to do this by giving precedence to the formatter specified on the
+    command line and override the one in the profile.
+
+    Given the following profiles are defined:
+      """
+      default: features/sample.feature --require features/support/env.rb -v --format profile
+      """
+    When I run cucumber features --format pretty
+    And the output should contain
+      """
+      Feature: Sample
+      """
+
+
+
+

data/features/rake_task.feature

@@ -148,3 +148,31 @@ Feature: Rake task
       """
         * features/support/dont_require_me.rb
       """
+
+  Scenario: feature files with spaces
+    Given a file named "features/spaces are nasty.feature" with:
+       """
+       Feature: The futures green
+
+         Scenario: Orange
+           Given this is missing
+       """
+    And a file named "Rakefile" with:
+       """
+       $LOAD_PATH.unshift(CUCUMBER_LIB)
+       require 'cucumber/rake/task'
+
+       Cucumber::Rake::Task.new(:features) do |t|
+         t.cucumber_opts = %w{--quiet --no-color}
+       end
+       """
+    When I run rake features
+    Then it should pass
+    And the output should contain
+       """
+       Feature: The futures green
+
+         Scenario: Orange
+           Given this is missing
+
+       """

data/features/step_definitions/cucumber_steps.rb

@@ -39,7 +39,6 @@ Given /^I am not running (?:.*) in the background$/ do
   # no-op
 end
 
-
 When /^I run cucumber (.*)$/ do |cucumber_opts|
   run "#{Cucumber::RUBY_BINARY} #{Cucumber::BINARY} --no-color #{cucumber_opts}"
 end
@@ -75,23 +74,17 @@ Then /^the output should be$/ do |text|
   last_stdout.should == text
 end
 
-Then /^"(.*)" should contain XML$/ do |file, xml|
-  t = Tempfile.new('cucumber-junit')
-  t.write(xml)
-  t.flush
-  t.close
-  cmd = "diffxml #{t.path} #{file}"
-  diff = `#{cmd}`
-  if diff =~ /<delta>/m
-    raise diff + "\nXML WAS:\n" + IO.read(file)
-  end
+Then /^"([^\"]*)" should contain$/ do |file, text|
+  strip_duration(IO.read(file)).should == text
 end
 
-Then /^"(.*)" should contain$/ do |file, text|
-  strip_duration(IO.read(file)).should == text
+Then /^"([^\"]*)" with junit duration "([^\"]*)" should contain$/ do |actual_file, duration_replacement, text|
+  actual = IO.read(actual_file)
+  actual = replace_junit_duration(actual, duration_replacement)
+  actual.should == text
 end
 
-Then /^"(.*)" should match$/ do |file, text|
+Then /^"([^\"]*)" should match$/ do |file, text|
   IO.read(file).should =~ Regexp.new(text)
 end
 
@@ -111,11 +104,15 @@ Then /^STDERR should not match$/ do |text|
   last_stderr.should_not =~ /#{text}/
 end
 
+Then /^STDERR should be$/ do |text|
+  last_stderr.should == text
+end
+
 Then /^STDERR should be empty$/ do
   last_stderr.should == ""
 end
 
-Then /^"(.*)" should exist$/ do |file|
+Then /^"([^\"]*)" should exist$/ do |file|
   File.exists?(file).should be_true
   FileUtils.rm(file)
 end
@@ -128,3 +125,19 @@ Then /^"([^\"]*)" should be required$/ do |file_name|
   last_stdout.should include("* #{file_name}")
 end
 
+Then /^exactly these files should be loaded:\s*(.*)$/ do |files|
+  last_stdout.scan(/^  \* (.*\.rb)$/).flatten.should == files.split(/,\s+/)
+end
+
+Then /^exactly these features should be ran:\s*(.*)$/ do |files|
+  last_stdout.scan(/^  \* (.*\.feature)$/).flatten.should == files.split(/,\s+/)
+end
+
+Then /^the (.*) profile should be used$/ do |profile|
+  last_stdout.should =~ /Using the #{profile} profile/
+end
+
+Then /^print output$/ do
+  puts last_stdout
+end
+

data/features/steps_formatter.feature

@@ -0,0 +1,25 @@
+Feature: --formatter steps option - Steps Formatter
+  In order to easily see which steps are already defined,
+  specially when using 3rd party steps libraries,
+  Cucumber should show the available steps in a user-friendly format
+
+  Background:
+    Given I am in steps_library
+
+  Scenario: Printing steps
+    When I run cucumber -f steps features
+    Then it should pass with
+    """
+    features/step_definitions/steps_lib1.rb
+      /^I defined a first step$/           # features/step_definitions/steps_lib1.rb:1
+      /^I define a second step$/           # features/step_definitions/steps_lib1.rb:4
+      /^I should also have a third step$/  # features/step_definitions/steps_lib1.rb:7
+    
+    features/step_definitions/steps_lib2.rb
+      /^I defined a step 4$/                # features/step_definitions/steps_lib2.rb:1
+      /^I create a step 5$/                 # features/step_definitions/steps_lib2.rb:4
+      /^I should be too tired for step 6$/  # features/step_definitions/steps_lib2.rb:7
+    
+    6 step definition(s) in 2 source file(s).
+
+    """

data/features/support/env.rb

@@ -50,6 +50,10 @@ class CucumberWorld
     s.gsub(/\d+m\d+\.\d+s/m, replacement)
   end
 
+  def replace_junit_duration(s, replacement)
+    s.gsub(/\d+\.\d\d+/m, replacement)
+  end
+
   def create_file(file_name, file_content)
     file_content.gsub!("CUCUMBER_LIB", "'#{cucumber_lib_dir}'") # Some files, such as Rakefiles need to use the lib dir
     in_current_dir do
@@ -70,6 +74,11 @@ class CucumberWorld
     stderr_file.close
     in_current_dir do
       @last_stdout = `#{command} 2> #{stderr_file.path}`
+      mode = Cucumber::RUBY_1_9 ? {:external_encoding=>"UTF-8"} : 'r'
+      IO.popen("#{command} 2> #{stderr_file.path}", mode) do |io|
+        @last_stdout = io.read
+      end
+
       @last_exit_status = $?.exitstatus
     end
     @last_stderr = IO.read(stderr_file.path)
@@ -113,8 +122,3 @@ end
 After do
   terminate_background_jobs
 end
-
-Before('@diffxml') do
-  `diffxml --version`
-  raise "Please install diffxml from http://diffxml.sourceforge.net/" if $? != 0
-end

data/features/table_diffing.feature

@@ -0,0 +1,45 @@
+Feature: Table diffing
+  In order to more easily compare data in tables
+  step definition writers should be able to diff
+  a table with expected data and see the diff inline
+  
+  Scenario: Extra row
+    Given a standard Cucumber project directory structure
+    And a file named "features/tables.feature" with:
+      """
+      Feature: Tables
+        Scenario: Extra row
+          Then the table should be:
+            | x | y |
+            | a | b |
+      """
+    And a file named "features/step_definitions/table_steps.rb" with:
+      """
+      Then /the table should be:/ do |expected|
+        expected.diff!(table(%{
+          | x | y | 
+          | a | c |
+        }))
+      end
+      """
+    When I run cucumber -i features/tables.feature
+    Then it should fail with
+      """
+      Feature: Tables
+      
+        Scenario: Extra row         # features/tables.feature:2
+          Then the table should be: # features/step_definitions/table_steps.rb:1
+            | x | y |
+            | a | b |
+            | a | c |
+            Tables were not identical (RuntimeError)
+            ./features/step_definitions/table_steps.rb:2:in `/the table should be:/'
+            features/tables.feature:3:in `Then the table should be:'
+      
+      Failing Scenarios:
+      cucumber features/tables.feature:2 # Scenario: Extra row
+
+      1 scenario (1 failed)
+      1 step (1 failed)
+
+      """

data/features/unicode_table.feature

@@ -0,0 +1,35 @@
+Feature: Unicode in tables
+  In order to please the whole world,
+  unicode characters in tables should be
+  properly aligned
+  
+  Scenario: All sorts of weird stuff
+    Given a standard Cucumber project directory structure
+    And a file named "features/unicode.feature" with:
+      """
+      Feature: Featuring unicode
+
+        Scenario: So what, whatever
+          Given passing
+            | Brüno | abc |
+            | Bruno | æøå |
+      """
+    And a file named "features/env.rb" with:
+      """
+      $KCODE='u'
+      """
+    When I run cucumber -q --dry-run features/unicode.feature
+    Then it should pass with
+      """
+      Feature: Featuring unicode
+
+        Scenario: So what, whatever
+          Given passing
+            | Brüno | abc |
+            | Bruno | æøå |
+
+      1 scenario (1 undefined)
+      1 step (1 undefined)
+
+      """
+    

data/features/work_in_progress.feature

@@ -52,6 +52,7 @@ Feature: Cucumber --work-in-progress switch
   @mri186
   Scenario: Pass with Failing Scenarios
     When I run cucumber -q -w -t @failing features/wip.feature
+    Then STDERR should be empty
     Then it should pass with
       """
       Feature: WIP

data/gem_tasks/contributors.rake

@@ -0,0 +1,4 @@
+task :contributors do
+  contributors = `git log --pretty=short --no-merges | git shortlog -ne | egrep -ve '^ +' | egrep -ve '^$'`
+  puts contributors.split("\n").length
+end

data/lib/cucumber/ast/background.rb

@@ -23,6 +23,7 @@ module Cucumber
       end
 
       def accept(visitor)
+        return if $cucumber_interrupted
         visitor.visit_comment(@comment) unless @comment.empty?
         visitor.visit_background_name(@keyword, @name, file_colon_line(@line), source_indent(first_line_length))
         visitor.step_mother.before(hook_context)

data/lib/cucumber/ast/comment.rb

@@ -17,6 +17,7 @@ module Cucumber
       end
 
       def accept(visitor)
+        return if $cucumber_interrupted
         @value.strip.split("\n").each do |line|
           visitor.visit_comment_line(line.strip)
         end