Feature: Bootstrapping a new project
  In order to have the best chances of getting up and running with cucumber
  As a new cucumber user
  I want cucumber to give helpful error messages in basic situations

 Scenario: running cucumber against a non-existing feature file
  Given a directory without standard Cucumber project directory structure
    When I run `cucumber`
    Then it should fail with:
      """
      No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)
      """

 Scenario: does not load ruby files in root if features directory is missing
  Given a directory without standard Cucumber project directory structure
  And a file named "should_not_load.rb" with:
    """
    puts 'this will not be shown'
    """
  When I run `cucumber`
  Then it should fail with exactly:
    """
    No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)

    """

Feature: Bootstrapping a new project
  In order to have the best chances of getting up and running with cucumber
  As a new cucumber user
  I want cucumber to give helpful error messages in basic situations

 @spawn
 Scenario: running cucumber against a non-existing feature file
  Given a directory without standard Cucumber project directory structure
    When I run `cucumber`
    Then it should fail with:
      """
      No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)
      """

 @spawn
 Scenario: does not load ruby files in root if features directory is missing
  Given a directory without standard Cucumber project directory structure
  And a file named "should_not_load.rb" with:
    """
    puts 'this will not be shown'
    """
  When I run `cucumber`
  Then it should fail with exactly:
    """
    No such file or directory - features. Please create a features directory to get started. (Errno::ENOENT)

    """

Add @spawn for Jruby access denied errors
Add @spawn for Jruby access denied errors
