Merge pull request #916 from cucumber/simplify-interactive-scenario

Simplify scenario describing interactive debugging

features/03_testing_frameworks/cucumber/steps/command/debug_your_command_in_aruba.feature

@@ -7,7 +7,6 @@ Feature: Debug your command in cucumber-test-run
     Given I use a fixture named "cli-app"
     And the default aruba exit timeout is 60 seconds
 
-  @unsupported-on-platform-java
   Scenario: You can use a debug repl in your cli program
 
     If you want to debug an error, which only occurs in one of your
@@ -19,26 +18,17 @@ Feature: Debug your command in cucumber-test-run
     program. However, Aruba steps that access the input and output of your
     program will not work.
 
-    Please make sure, that there's a statement after the `binding.pry`-call.
-    Otherwise you might not get an interactive shell, because your program will
-    just exit.
-
     We are going to demonstrate this using `pry`, but any other interactive
     debugger for any other programming language should also work.
 
     Given an executable named "bin/aruba-test-cli" with:
     """ruby
     #!/usr/bin/env ruby
 
-    $stderr.sync = true
-    $stdout.sync = true
-
     foo = 'hello'
 
     require 'pry'
     binding.pry
-
-    exit 0
     """
     And a file named "features/debug.feature" with:
     """cucumber