media-path 0.1

data/vendor/rspec/features/mock_framework_integration/use_rr.feature

@@ -0,0 +1,27 @@
+Feature: mock with rr
+
+  As an RSpec user who prefers rr
+  I want to be able to use rr without rspec mocks interfering
+
+  Scenario: Mock with rr
+    Given a file named "rr_example_spec.rb" with:
+      """
+      Spec::Runner.configure do |config|
+        config.mock_with :rr
+      end
+
+      describe "plugging in rr" do
+        it "allows rr to be used" do
+          target = Object.new
+          mock(target).foo
+          target.foo
+        end
+
+        it "does not include rspec mocks" do
+          Spec.const_defined?(:Mocks).should be_false
+        end
+      end
+      """
+    When I run "spec rr_example_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "2 examples, 0 failures"

data/vendor/rspec/features/mocks/block_local_expectations.feature

@@ -0,0 +1,62 @@
+Feature: block local expectations
+
+  In order to set message expectations on ...
+  As an RSpec user
+  I want to configure the evaluation context
+
+  Background:
+    Given a file named "account.rb" with:
+      """
+      class Account
+        def self.create
+          yield new
+        end
+
+        def opening_balance(amount, currency)
+        end
+      end
+      """
+
+  Scenario: passing example
+    Given a file named "account_dsl.rb" with:
+      """
+      require 'spec_helper'
+      require 'account'
+
+      describe "account DSL" do
+        it " .... " do
+          account = Account.new
+          Account.should_receive(:create).and_yield do |account|
+            account.should_receive(:opening_balance).with(100, :USD)
+          end
+          Account.create do
+            opening_balance 100, :USD
+          end
+        end
+      end
+      """
+    When I run "spec account_dsl.rb"
+    Then the stdout should include "1 example, 0 failures"
+    
+  Scenario: failing example
+    
+    Given a file named "account_dsl.rb" with:
+      """
+      require 'spec_helper'
+      require 'account'
+
+      describe "account DSL" do
+        it " .... " do
+          account = Account.new
+          Account.should_receive(:create).and_yield do |account|
+            account.should_receive(:opening_balance).with(100, :USD)
+          end
+          Account.create do
+            # opening_balance is not called here
+          end
+        end
+      end
+      """
+
+    When I run "spec account_dsl.rb"
+    Then the stdout should include "1 example, 1 failure"

data/vendor/rspec/features/mocks/mix_stubs_and_mocks.feature

@@ -0,0 +1,22 @@
+Feature: stub and mock together
+
+  As an RSpec user
+  I want to use stubs and mocks together
+
+  Scenario: stub in before
+    Given a file named "stub_and_mocks_spec.rb" with:
+      """
+      describe "a stub in before" do
+        before(:each) do
+          @messenger = mock('messenger').as_null_object
+        end
+
+        it "a" do
+          @messenger.should_receive(:foo).with('first')
+          @messenger.foo('second')
+          @messenger.foo('third')
+        end
+      end
+      """
+    When I run "spec stub_and_mocks_spec.rb --format nested"
+    Then the stdout should include "received :foo with unexpected arguments\n  expected: (\"first\")\n       got: ([\"second\"], [\"third\"])"

data/vendor/rspec/features/mocks/stub_implementation.feature

@@ -0,0 +1,26 @@
+Feature: stub implementation
+
+  As an rspec user, I want to stub a complete implementation, not just a
+  return value.
+  
+  Scenario: stub implementation
+    Given a file named "stub_implementation.rb" with:
+      """
+      describe "a stubbed implementation" do
+        it "works" do
+          object = Object.new
+          object.stub(:foo) do |arg|
+            if arg == :this
+              "got this"
+            elsif arg == :that
+              "got that"
+            end
+          end
+          
+          object.foo(:this).should == "got this"
+          object.foo(:that).should == "got that"
+        end
+      end
+      """
+    When I run "spec stub_implementation.rb"
+    Then the stdout should include "1 example, 0 failures"

data/vendor/rspec/features/pending/pending_examples.feature

@@ -0,0 +1,81 @@
+Feature: pending examples
+
+  RSpec offers three ways to indicate that an example is disabled pending
+  some action.
+
+  Scenario: pending implementation
+    Given a file named "example_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+      end
+      """
+    When I run "spec example_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "Not Yet Implemented"
+    And the stdout should include "example_without_block_spec.rb:2"
+
+  Scenario: pending implementation with spec/test/unit
+    Given a file named "example_without_block_spec.rb" with:
+      """
+      require 'spec/test/unit'
+      describe "an example" do
+        it "has not yet been implemented"
+      end
+      """
+    When I run "spec example_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "Not Yet Implemented"
+    And the stdout should include "example_without_block_spec.rb:3"
+
+  Scenario: pending any arbitary reason, with no block
+    Given a file named "pending_without_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished")
+        end
+      end
+      """
+    When I run "spec pending_without_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "(something else getting finished)"
+    And the stdout should include "pending_without_block_spec.rb:2"
+
+  Scenario: pending any arbitary reason, with a block that fails
+    Given a file named "pending_with_failing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            raise "this is the failure"
+          end
+        end
+      end
+      """
+    When I run "spec pending_with_failing_block_spec.rb"
+    Then the exit code should be 0
+    And the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "(something else getting finished)"
+    And the stdout should include "pending_with_failing_block_spec.rb:2"
+
+  Scenario: pending any arbitary reason, with a block that passes
+    Given a file named "pending_with_passing_block_spec.rb" with:
+      """
+      describe "an example" do
+        it "is implemented but waiting" do
+          pending("something else getting finished") do
+            true.should be(true)
+          end
+        end
+      end
+      """
+    When I run "spec pending_with_passing_block_spec.rb"
+    Then the exit code should be 256
+    And the stdout should include "1 example, 1 failure"
+    And the stdout should include "FIXED"
+    And the stdout should include "Expected pending 'something else getting finished' to fail. No Error was raised."
+    And the stdout should include "pending_with_passing_block_spec.rb:3"

data/vendor/rspec/features/runner/specify_line_number.feature

@@ -0,0 +1,32 @@
+Feature: run specific examples by line number
+
+  In order to run a single example from command line
+  RSpec allows you to specify the line number of the example(s) to run
+
+  Scenario: --line syntax on single example
+    Given a file named "example_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+        it "has been implemented" do
+          true
+        end
+      end
+      """
+    When I run "spec example_spec.rb --line 2"
+    Then the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "example_spec.rb:2"
+
+  Scenario: colon line syntax on single example
+    Given a file named "example_spec.rb" with:
+      """
+      describe "an example" do
+        it "has not yet been implemented"
+        it "has been implemented" do
+          true
+        end
+      end
+      """
+    When I run "spec example_spec.rb:2"
+    Then the stdout should include "1 example, 0 failures, 1 pending"
+    And the stdout should include "example_spec.rb:2"

data/vendor/rspec/features/spec_helper/spec_helper.feature

@@ -0,0 +1,25 @@
+Feature: spec helper
+  In order to centralize code needed across most specs
+  As a spec author
+  I want to require 'spec_helper'
+  
+  Because rspec adds the PROJECT_ROOT/spec directory to the load path, we can
+  just require 'spec_helper' and it will be found.
+
+  Scenario: spec helper
+    Given a directory named "spec"
+    And a file named "spec/spec_helper.rb" with:
+      """
+      SOME_CONSTANT = 'some value'
+      """
+    And a file named "example.rb" with:
+      """
+      require 'spec_helper'
+      describe SOME_CONSTANT do
+        it { should == 'some value' }
+      end
+      """
+    When I run "spec example.rb"
+    And  the stdout should include "1 example, 0 failures"
+    And  the exit code should be 0
+

data/vendor/rspec/features/step_definitions/running_rspec_steps.rb

@@ -0,0 +1,43 @@
+Given %r{^a file named "([^"]+)" with:$} do |file_name, code|
+  create_file(file_name, code)
+end
+
+Given /^a directory named "([^\"]*)"$/ do |dirname|
+  create_directory(dirname)
+end
+
+When %r{^I run "spec ([^"]+)"$} do |file_and_args|
+  spec(file_and_args)
+end
+
+When %r{^I run "ruby ([^"]+)"$} do |file_and_args|
+  ruby(file_and_args)
+end
+
+When %r{^I run "cmdline.rb ([^"]+)"$} do |file_and_args|
+  cmdline(file_and_args)
+end
+
+Then /^the (.*) should include (.*)$/ do |stream, string_or_regex|
+  written = case(stream)
+    when 'stdout' then last_stdout
+    when 'stderr' then last_stderr
+    else raise "Unknown stream: #{stream}"
+  end
+  written.should smart_match(string_or_regex)
+end
+
+Then /^the (.*) should not match (.*)$/ do |stream, string_or_regex|
+  written = case(stream)
+    when 'stdout' then last_stdout
+    when 'stderr' then last_stderr
+    else raise "Unknown stream: #{stream}"
+  end
+  written.should_not smart_match(string_or_regex)
+end
+
+Then /^the exit code should be (\d+)$/ do |exit_code|
+  if last_exit_code != exit_code.to_i
+    raise "Did not exit with #{exit_code}, but with #{last_exit_code}. Standard error:\n#{last_stderr}"
+  end
+end

data/vendor/rspec/features/subject/explicit_subject.feature

@@ -0,0 +1,31 @@
+Feature: explicit subject
+
+  You can override the implicit subject using the subject() method.
+  
+  Scenario: subject in top level group
+    Given a file named "top_level_subject_spec.rb" with:
+      """
+      describe Array, "with some elements" do
+        subject { [1,2,3] }
+        it "should have the prescribed elements" do
+          subject.should == [1,2,3]
+        end
+      end
+      """
+    When I run "spec top_level_subject_spec.rb"
+    Then the stdout should include "1 example, 0 failures"
+
+  Scenario: subject in a nested group
+    Given a file named "nested_subject_spec.rb" with:
+      """
+      describe Array do
+        subject { [1,2,3] }
+        describe "with some elements" do
+          it "should have the prescribed elements" do
+            subject.should == [1,2,3]
+          end
+        end
+      end
+      """
+    When I run "spec nested_subject_spec.rb"
+    Then the stdout should include "1 example, 0 failures"

data/vendor/rspec/features/subject/implicit_subject.feature

@@ -0,0 +1,43 @@
+Feature: implicit subject
+
+  The first argument to the outermost example group block is
+  made available to each example as an implicit subject of
+  that example.
+  
+  Scenario: subject in top level group
+    Given a file named "top_level_subject_spec.rb" with:
+      """
+      describe Array, "when first created" do
+        it "should be empty" do
+          subject.should == []
+        end
+      end
+      """
+    When I run "spec top_level_subject_spec.rb"
+    Then the stdout should include "1 example, 0 failures"
+
+  Scenario: subject in a nested group
+    Given a file named "nested_subject_spec.rb" with:
+      """
+      describe Array do
+        describe "when first created" do
+          it "should be empty" do
+            subject.should == []
+          end
+        end
+      end
+      """
+    When I run "spec nested_subject_spec.rb"
+    Then the stdout should include "1 example, 0 failures"
+
+  Scenario: subject with getters
+    Given a file named "subject_with_getter_spec.rb" with:
+      """
+      describe Array do
+        describe "when first created" do
+          its(:length) { should == 0 }
+        end
+      end
+      """
+    When I run "spec subject_with_getter_spec.rb"
+    Then the stdout should include "1 example, 0 failures"

data/vendor/rspec/features/support/env.rb

@@ -0,0 +1,82 @@
+$:.unshift File.join(File.dirname(__FILE__), "/../../lib")
+
+require 'spec/expectations'
+require 'forwardable'
+require 'tempfile'
+require 'spec/ruby_forker'
+require 'features/support/matchers/smart_match'
+
+class RspecWorld
+  include Spec::Expectations
+  include Spec::Matchers
+  include RubyForker
+
+  extend Forwardable
+  def_delegators RspecWorld, :working_dir, :spec_command, :cmdline_file, :rspec_lib
+
+  def self.working_dir
+    @working_dir ||= File.expand_path(File.join(File.dirname(__FILE__), "/../../tmp/cucumber-generated-files"))
+  end
+
+  def self.spec_command
+    @spec_command ||= File.expand_path(File.join(File.dirname(__FILE__), "/../../bin/spec"))
+  end
+
+  def self.cmdline_file
+    @cmdline_file ||= File.expand_path(File.join(File.dirname(__FILE__), "/../../resources/helpers/cmdline.rb"))
+  end
+
+  def self.rspec_lib
+    @rspec_lib ||= File.join(working_dir, "/../../lib")
+  end
+
+  def spec(args)
+    ruby("#{spec_command} #{args}")
+  end
+
+  def cmdline(args)
+    ruby("#{cmdline_file} #{args}")
+  end
+
+  def create_file(file_name, contents)
+    file_path = File.join(working_dir, file_name)
+    File.open(file_path, "w") { |f| f << contents }
+  end
+
+  def create_directory(dirname)
+    FileUtils.mkdir_p File.join(working_dir, dirname)
+  end
+
+  def last_stdout
+    @stdout
+  end
+
+  def last_stderr
+    @stderr
+  end
+
+  def last_exit_code
+    @exit_code
+  end
+
+  # it seems like this, and the last_* methods, could be moved into RubyForker-- is that being used anywhere but the features?
+  def ruby(args)
+    stderr_file = Tempfile.new('rspec')
+    stderr_file.close
+    Dir.chdir(working_dir) do
+      @stdout = super("-I #{rspec_lib} #{args}", stderr_file.path)
+    end
+    @stderr = IO.read(stderr_file.path)
+    @exit_code = $?.to_i
+  end
+
+end
+
+Before do
+  FileUtils.rm_rf   RspecWorld.working_dir if test ?d, RspecWorld.working_dir
+  FileUtils.mkdir_p RspecWorld.working_dir
+end
+
+World do
+  RspecWorld.new
+end