features/docs/defining_steps/nested_steps.feature in cucumber-3.0.0.pre.1 vs features/docs/defining_steps/nested_steps.feature in cucumber-3.0.0.pre.2

@@ -10,10 +10,11 @@
       Given /a turtle/ do
         puts "turtle!"
       end
       """
 
+  @todo-windows
   Scenario: Use #steps to call several steps at once
     Given a step definition that looks like this:
       """ruby
       Given /two turtles/ do
         steps %{
@@ -29,10 +30,11 @@
 
       turtle!
 
       """
 
+  @todo-windows
   Scenario: Use #step to call a single step
     Given a step definition that looks like this:
       """ruby
       Given /two turtles/ do
         step "a turtle"
@@ -46,10 +48,11 @@
 
       turtle!
 
       """
 
+  @todo-windows
   Scenario: Use #steps to call a table
     Given a step definition that looks like this:
       """ruby
       Given /turtles:/ do |table|
         table.hashes.each do |row|
@@ -75,10 +78,11 @@
 
       Liouville
 
       """
 
+  @todo-windows
   Scenario: Use #steps to call a multi-line string
     Given a step definition that looks like this:
       """ruby
         Given /two turtles/ do
           steps %Q{
@@ -101,10 +105,10 @@
       """
       Sturm
       Liouville
       """
 
-  @spawn
+  @spawn @todo-windows
   Scenario: Backtrace doesn't skip nested steps
     Given a step definition that looks like this:
       """ruby
       Given /two turtles/ do
         step "I have a couple turtles"