Merge branch 'release/0.2.0'

ruby-gem/crudecumber.gemspec

@@ -1,15 +1,15 @@
 Gem::Specification.new do |s|
   s.name        = 'crudecumber'
-  s.version     = '0.1.5'
-  s.date        = '2015-06-21'
-  s.summary     = 'Crudecumber 0.1.5'
+  s.version     = '0.2.0'
+  s.date        = Date.today.to_s
+  s.summary     = 'Crudecumber 0.2.0'
   s.description = "Manually run through your Cucumber scenarios.\n
   Run exactly as you would run Cucumber but instead use \'crudecumber\' followed
   by your usual arguments."
   s.author      = ['Dan Buckland']
-  s.email       = '[email protected]'
+  s.email       = '[email protected]'
   s.files       = Dir['lib/**/**/*'] + Dir['bin/*']
-  s.homepage    = 'https://github.com/danbuckland/crudecumber'
+  s.homepage    = 'http://crudecumber.xyz'
   s.license     = 'MIT'
   s.platform    = Gem::Platform::RUBY
   s.required_ruby_version = '>= 1.9.3'

features/example.feature → ruby-gem/features/example.feature

@@ -9,7 +9,7 @@ Feature: Running any Cucumber scenarios with the Crudecumber gem
     When I run 'crudecumber'
     Then I should be able to step through my scenarios manually
 
-  @bugs @#2
+  @bugs @2
   Scenario: Ignore local step definitions to avoid ambiguous matches
     Given I have local step definitions for this step
     And a default profile explicitly requiring the step_definitions folder
@@ -20,9 +20,9 @@ Feature: Running any Cucumber scenarios with the Crudecumber gem
   @tables
   Scenario: Allow testers to manually run scenarios with tables
     Given I have a scenario that contains the following table:
-      | Javan Slow Loris    |
-      | Rondo Dwarf Galago  |
-      | Brown Spider Monkey |
+    | Javan Slow Loris    |
+    | Rondo Dwarf Galago  |
+    | Brown Spider Monkey |
     When I run 'crudecumber'
     Then I should be able to step through this scenario manually
 

ruby-gem/features/scenario_with_background.feature

@@ -0,0 +1,21 @@
+Feature: Running any scenarios with backgrounds using the Crudecumber gem
+
+  Running version 0.1.5 of Crudecumber with scenarios that have background steps
+  can cause the background step to remain visible when the first scenario step
+  is run. This only happens when the last background step is longer than the
+  first scenario step.
+
+  Background: Precede scenario with long background step
+    Given I have a rather verbose and therefore lengthy first background step
+    And I have a long second step that's not quite as long as the first one
+
+  @bugs @7
+  Scenario: Scenario steps should not overlap last background step
+    When I start a scenario with a short step
+    Then I should not see the background step behind
+
+  @bugs @7
+  Scenario: Scenario steps should not overlap last background step
+    When I start a different scenario
+    And that scenario also has a short first step
+    Then I should not see the background step behind

ruby-gem/lib/crudecumber/support/crudecumber_formatter.rb

@@ -10,12 +10,12 @@ module Crudecumber
   # SlowHandCuke formatter) and stops irrelevant Ruby errors being displayed.
   class Formatter < Cucumber::Formatter::Pretty
     def before_step(step)
-      @io.printf "... #{step.name}"
+      @io.printf "#{step.keyword}#{step.name}".indent(@scenario_indent + 2)
       @io.flush
     end
 
     def before_step_result(*args)
-      @io.printf "\r"
+      @io.printf "\r\033[K"
       super
     end