cucover 0.1.2

data/examples/self_test/rails/public/robots.txt

@@ -0,0 +1,5 @@
+# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
+#
+# To ban all spiders from the entire site uncomment the next two lines:
+# User-Agent: *
+# Disallow: /

data/examples/self_test/rails/script/about

@@ -0,0 +1,4 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+$LOAD_PATH.unshift "#{RAILTIES_PATH}/builtin/rails_info"
+require 'commands/about'

data/examples/self_test/rails/script/console

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/console'

data/examples/self_test/rails/script/cucumber

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+vendored_cucumber_bin = Dir["#{File.dirname(__FILE__)}/../vendor/{gems,plugins}/cucumber*/bin/cucumber"].first
+if vendored_cucumber_bin
+  load File.expand_path(vendored_cucumber_bin)
+else
+  require 'rubygems' unless ENV['NO_RUBYGEMS']
+  require 'cucumber'
+  load Cucumber::BINARY
+end

data/examples/self_test/rails/script/dbconsole

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/dbconsole'

data/examples/self_test/rails/script/destroy

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/destroy'

data/examples/self_test/rails/script/generate

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/generate'

data/examples/self_test/rails/script/performance/benchmarker

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../../config/boot',  __FILE__)
+require 'commands/performance/benchmarker'

data/examples/self_test/rails/script/performance/profiler

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../../config/boot',  __FILE__)
+require 'commands/performance/profiler'

data/examples/self_test/rails/script/plugin

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/plugin'

data/examples/self_test/rails/script/runner

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/runner'

data/examples/self_test/rails/script/server

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+require File.expand_path('../../config/boot',  __FILE__)
+require 'commands/server'

data/examples/self_test/simple/features/call_foo.feature

@@ -0,0 +1,4 @@
+Feature: Call Foo
+  
+  Scenario: Call Foo
+    When I call Foo

data/examples/self_test/simple/features/call_foo_and_bar_together.feature

@@ -0,0 +1,5 @@
+Feature: Call Foo and Bar Together
+  
+  Scenario: Call Foo and Bar
+    When I call Foo
+    And I call Bar

data/examples/self_test/simple/features/call_foo_from_background_then_bar.feature

@@ -0,0 +1,7 @@
+Feature: Call Foo from Background then Bar
+
+  Background:
+    Given I have called Foo
+
+  Scenario: Call Bar
+    When I call Bar

data/examples/self_test/simple/features/call_foo_from_background_then_bar_then_baz.feature

@@ -0,0 +1,10 @@
+Feature: Call Foo from Background then Bar then Baz
+
+  Background:
+    Given I have called Foo
+
+  Scenario: Call Bar
+    When I call Bar
+
+  Scenario: Call Baz
+    When I call Baz

data/examples/self_test/simple/features/call_foo_then_bar.feature

@@ -0,0 +1,7 @@
+Feature: Call Foo then Bar
+
+  Scenario: Call Foo
+    When I call Foo
+
+  Scenario: Call Bar
+    When I call Bar

data/examples/self_test/simple/features/call_foo_then_bar_from_scenario_outline_examples.feature

@@ -0,0 +1,9 @@
+Feature: Call Foo then Bar from Scenario Outline Examples
+
+  Scenario Outline: Call Something
+    When I call <Code>
+    
+    Examples: 
+      | Code |
+      | Foo  |
+      | Bar  |

data/examples/self_test/simple/features/fail.feature

@@ -0,0 +1,10 @@
+Feature: Epic Fail
+  In order to make my job look really hard
+  As a developer
+  I want tests to fail from time to time
+  
+  Scenario: Do something stupid
+    When I divide by zero
+  
+
+  

data/examples/self_test/simple/features/step_definitions/main_steps.rb

@@ -0,0 +1,15 @@
+require File.dirname(__FILE__) + '/../../lib/foo'
+require File.dirname(__FILE__) + '/../../lib/bar'
+require File.dirname(__FILE__) + '/../../lib/baz'
+
+Given /^I have called ([\w]+)$/ do |class_name|
+  Object.const_get(class_name).new.execute
+end
+
+When /^I call ([\w]+)$/ do |class_name|
+  Given "I have called #{class_name}"
+end
+
+When /^I divide by zero$/ do
+  1/0
+end

data/examples/self_test/simple/lib/bar.rb

@@ -0,0 +1,5 @@
+class Bar
+  def execute
+    true
+  end
+end

data/examples/self_test/simple/lib/baz.rb

@@ -0,0 +1,5 @@
+class Baz
+  def execute
+    true
+  end
+end

data/examples/self_test/simple/lib/foo.rb

@@ -0,0 +1,9 @@
+class Foo
+  def execute
+    true
+  end
+
+  def sloppy_method
+    1/0
+  end
+end

data/features/coverage_of.feature

@@ -0,0 +1,81 @@
+Feature: Coverage Of
+  In order to find out how well tested a source file that I'm working on is
+  As a developer
+  I want to be able to ask Cucover which features cover which lines of a given source file
+
+  Background:
+    Given I am using the simple example app
+
+  @ruby_1_8
+  Scenario: Get coverage of a source file that's partly touched by the feature that was run
+    Given I have run cucover -- features/call_foo.feature
+    When I run cucover --coverage-of lib/foo.rb
+    Then it should pass with:
+    """
+    1 class Foo
+    2   def execute     features/call_foo.feature:3
+    3     true          features/call_foo.feature:3
+    4   end
+    5
+    6   def sloppy_me..
+    7     1/0
+    8   end
+    9 end
+
+    """
+
+  @ruby_1_8
+  Scenario: Run another feature that also covers the same source file
+    Given I have run cucover -- features/call_foo.feature
+    And I have run cucover -- features/call_foo_and_bar_together.feature
+    When I run cucover --coverage-of lib/foo.rb
+    Then it should pass with:
+    """
+    1 class Foo
+    2   def execute     features/call_foo_and_bar_together.feature:3, features/call_foo.feature:3
+    3     true          features/call_foo_and_bar_together.feature:3, features/call_foo.feature:3
+    4   end
+    5
+    6   def sloppy_me..
+    7     1/0
+    8   end
+    9 end
+
+    """
+
+  @ruby_1_9
+  Scenario: Get coverage of a source file that's partly touched by the feature that was run
+    Given I have run cucover -- features/call_foo.feature
+    When I run cucover --coverage-of lib/foo.rb
+    Then it should pass with:
+    """
+    1 class Foo
+    2   def execute     features/call_foo.feature:3
+    3     true          features/call_foo.feature:3
+    4   end             features/call_foo.feature:3
+    5
+    6   def sloppy_me..
+    7     1/0
+    8   end
+    9 end
+
+    """
+
+  @ruby_1_9
+  Scenario: Run another feature that also covers the same source file
+    Given I have run cucover -- features/call_foo.feature
+    And I have run cucover -- features/call_foo_and_bar_together.feature
+    When I run cucover --coverage-of lib/foo.rb
+    Then it should pass with:
+    """
+    1 class Foo
+    2   def execute     features/call_foo.feature:3, features/call_foo_and_bar_together.feature:3
+    3     true          features/call_foo.feature:3, features/call_foo_and_bar_together.feature:3
+    4   end             features/call_foo.feature:3, features/call_foo_and_bar_together.feature:3
+    5
+    6   def sloppy_me..
+    7     1/0
+    8   end
+    9 end
+
+    """

data/features/fail.feature

@@ -0,0 +1,60 @@
+Feature: Fail
+  In order to diagnose a fault
+  As a developer
+  I want to get useful information when a feature fails
+  
+  Scenario: Two features, one fails
+    And I am using the simple example app
+    When I run cucover -- features/call_foo.feature features/fail.feature
+    Then it should fail with:
+      """
+      Feature: Call Foo
+      
+        Scenario: Call Foo # features/call_foo.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+      
+      Feature: Epic Fail
+        In order to make my job look really hard
+        As a developer
+        I want tests to fail from time to time
+      
+        Scenario: Do something stupid # features/fail.feature:6
+          When I divide by zero       # features/step_definitions/main_steps.rb:13
+            divided by 0 (ZeroDivisionError)
+            ./features/step_definitions/main_steps.rb:14:in `/'
+            ./features/step_definitions/main_steps.rb:14:in `/^I divide by zero$/'
+            features/fail.feature:7:in `When I divide by zero'
+
+      Failing Scenarios:
+      cucumber features/fail.feature:6 # Scenario: Do something stupid
+      
+      2 scenarios (1 failed, 1 passed)
+      2 steps (1 failed, 1 passed)
+      
+      """
+  
+  Scenario: Run failing feature twice
+    And I am using the simple example app
+    And I have tried to run cucover -- features/fail.feature
+    When I run cucover -- features/fail.feature
+    Then it should fail with:
+    """
+    Feature: Epic Fail
+      In order to make my job look really hard
+      As a developer
+      I want tests to fail from time to time
+    
+      Scenario: Do something stupid # features/fail.feature:6
+        When I divide by zero       # features/step_definitions/main_steps.rb:13
+          divided by 0 (ZeroDivisionError)
+          ./features/step_definitions/main_steps.rb:14:in `/'
+          ./features/step_definitions/main_steps.rb:14:in `/^I divide by zero$/'
+          features/fail.feature:7:in `When I divide by zero'
+
+    Failing Scenarios:
+    cucumber features/fail.feature:6 # Scenario: Do something stupid
+    
+    1 scenario (1 failed)
+    1 step (1 failed)
+    
+    """

data/features/help.feature

@@ -0,0 +1,15 @@
+Feature: Showing help
+  In order to harness the full power of cucover
+  As a developer
+  I want to see help explaining cucovers usage
+  
+  Background:
+    Given I am using the simple example app
+  
+  Scenario: --help
+    When I run cucover --help
+    Then I should see "Usage: cucover -- [options] [ [FILE|DIR|URL][:LINE[:LINE]*] ]+"
+  
+  Scenario: invalid command line handle
+    When I run cucover --invalid-thingy
+    Then I should see "Usage: cucover -- [options] [ [FILE|DIR|URL][:LINE[:LINE]*] ]+"

data/features/lazy_run.feature

@@ -0,0 +1,76 @@
+Feature: Lazy Run
+  In order to get rapid feedback, stay motivated and keep my concentration
+  As a developer
+  I want to be able to run only the features that could have been affected by the changes I've made
+
+  Background:
+    And I am using the simple example app
+    And I have run cucover -- features/call_foo.feature
+
+  Scenario: Change nothing and run same feature again
+    When I run cucover -- -q features/call_foo.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo
+
+        Scenario: Call Foo
+          When I call Foo
+            [ Cucover - Skipping clean scenario ]
+
+      1 scenario (1 skipped)
+      1 step (1 skipped)
+
+      """
+
+  Scenario: Change irrelevant source file and run same feature again
+    When I edit the source file lib/bar.rb
+    When I run cucover -- features/call_foo.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo
+
+        Scenario: Call Foo # features/call_foo.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+      1 scenario (1 skipped)
+      1 step (1 skipped)
+
+      """
+
+  Scenario: Touch feature file and run same feature again
+    When I edit the source file features/call_foo.feature
+    And I run cucover -- features/call_foo.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo
+
+        Scenario: Call Foo # features/call_foo.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+
+      1 scenario (1 passed)
+      1 step (1 passed)
+
+      """
+
+  Scenario: Touch one source file and try to run lots of features
+    When I edit the source file lib/bar.rb
+    And I run cucover -- features/call_foo.feature features/call_foo_and_bar_together.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo
+
+        Scenario: Call Foo # features/call_foo.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+      Feature: Call Foo and Bar Together
+
+        Scenario: Call Foo and Bar # features/call_foo_and_bar_together.feature:3
+          When I call Foo          # features/step_definitions/main_steps.rb:9
+          And I call Bar           # features/step_definitions/main_steps.rb:9
+
+      2 scenarios (1 skipped, 1 passed)
+      3 steps (1 skipped, 2 passed)
+
+      """

data/features/lazy_run_per_scenario.feature

@@ -0,0 +1,108 @@
+Feature: Lazy Run per Scenario
+  In order to work with a single feature
+  As a developer
+  I want to skip the scenarios that don't need to be run
+
+  Background:
+    Given I am using the simple example app
+
+  Scenario: Change nothing and run same feature again
+    Given I have run cucover -- features/call_foo_then_bar.feature
+    When I run cucover -- features/call_foo_then_bar.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo then Bar
+
+        Scenario: Call Foo # features/call_foo_then_bar.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+        Scenario: Call Bar # features/call_foo_then_bar.feature:6
+          When I call Bar  # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+      2 scenarios (2 skipped)
+      2 steps (2 skipped)
+
+      """
+
+  Scenario: Edit source file covered by only one scenario and run same feature again
+    Given I have run cucover -- features/call_foo_then_bar.feature
+    When I edit the source file lib/foo.rb
+    And I run cucover -- features/call_foo_then_bar.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo then Bar
+
+        Scenario: Call Foo # features/call_foo_then_bar.feature:3
+          When I call Foo  # features/step_definitions/main_steps.rb:9
+
+        Scenario: Call Bar # features/call_foo_then_bar.feature:6
+          When I call Bar  # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+      2 scenarios (1 skipped, 1 passed)
+      2 steps (1 skipped, 1 passed)
+
+      """
+
+  Scenario: Run a feature with a background twice
+    Given I have run cucover -- features/call_foo_from_background_then_bar.feature
+    When I run cucover -- features/call_foo_from_background_then_bar.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo from Background then Bar
+
+        Background:               # features/call_foo_from_background_then_bar.feature:3
+          Given I have called Foo # features/step_definitions/main_steps.rb:5
+            [ Cucover - Skipping clean scenario ]
+
+        Scenario: Call Bar        # features/call_foo_from_background_then_bar.feature:6
+          When I call Bar         # features/step_definitions/main_steps.rb:9
+
+      1 scenario (1 skipped)
+      2 steps (2 skipped)
+
+      """
+
+  Scenario: Edit source file covered by the background of a feature
+    Given I have run cucover -- features/call_foo_from_background_then_bar.feature
+    When I edit the source file lib/foo.rb
+    And I run cucover -- features/call_foo_from_background_then_bar.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo from Background then Bar
+
+        Background:               # features/call_foo_from_background_then_bar.feature:3
+          Given I have called Foo # features/step_definitions/main_steps.rb:5
+
+        Scenario: Call Bar        # features/call_foo_from_background_then_bar.feature:6
+          When I call Bar         # features/step_definitions/main_steps.rb:9
+
+      1 scenario (1 passed)
+      2 steps (2 passed)
+
+      """
+
+  Scenario: Edit source file covered by a scenario with a background
+    Given I have run cucover -- features/call_foo_from_background_then_bar_then_baz.feature
+    When I edit the source file lib/bar.rb
+    And I run cucover -- features/call_foo_from_background_then_bar_then_baz.feature
+    Then it should pass with:
+      """
+      Feature: Call Foo from Background then Bar then Baz
+
+        Background:               # features/call_foo_from_background_then_bar_then_baz.feature:3
+          Given I have called Foo # features/step_definitions/main_steps.rb:5
+
+        Scenario: Call Bar        # features/call_foo_from_background_then_bar_then_baz.feature:6
+          When I call Bar         # features/step_definitions/main_steps.rb:9
+
+        Scenario: Call Baz        # features/call_foo_from_background_then_bar_then_baz.feature:9
+          When I call Baz         # features/step_definitions/main_steps.rb:9
+            [ Cucover - Skipping clean scenario ]
+
+      2 scenarios (1 skipped, 1 passed)
+      4 steps (2 skipped, 2 passed)
+
+      """