title: Rspec/Capybara "feature" method undefined when Guard runs specs in watched files, works when run manually
body: <p>I am getting a strange issue when using Guard to run my specs.</p>
  
  <p>I am running a feature spec that uses the Capybara "feature" / "scenario" syntax. I am also using Spring.</p>
  
  <p>Everything works fine if I run <code>rspec spec</code> or <code>spring rspec</code> in the console or <code>rspec</code> in the Guard shell. But, when the watched specs get run automatically by Guard, I get the following error:</p>
  
  <blockquote>
    <p>/spec/features/navigation_spec.rb:1:in <code>&lt;top (required)&gt;': undefined method</code>feature' for main:Object (NoMethodError)</p>
  </blockquote>
  
  <p>Why is it not picking up the Capybara syntax only in this specific context?</p>
  
  <p>Here is the relevant code:</p>
  
  <p>GuardFile</p>
  
  <pre><code>guard :rspec, :spring =&gt; true do
      watch(%r{^spec/.+_spec\.rb$})
  end
  </code></pre>
  
  <p>spec/features/navigation_spec.rb</p>
  
  <pre><code>feature "navigation" do
      context "When on the home page" do
          before { visit "/" }
  
          scenario "I should see the navigation header" do
              expect(page).to have_selector("div.navigation")
          end
      end
  end
  </code></pre>
  
  <p>spec/spec_helper.rb</p>
  
  <pre><code>require 'capybara/rspec'
  </code></pre>