spree 0.8.1 → 0.8.2

data/vendor/plugins/rspec/examples/passing/stubbing_example.rb

@@ -1,69 +0,0 @@
-require File.dirname(__FILE__) + '/spec_helper'
-
-describe "A consumer of a stub" do
-  it "should be able to stub methods on any Object" do
-    obj = Object.new
-    obj.stub!(:foobar).and_return {:return_value}
-    obj.foobar.should equal(:return_value)
-  end
-end
-
-class StubbableClass
-  def self.find id
-    return :original_return
-  end
-end
-
-describe "A stubbed method on a class" do
-  it "should return the stubbed value" do
-    StubbableClass.stub!(:find).and_return(:stub_return)
-    StubbableClass.find(1).should equal(:stub_return)
-  end
-  
-  it "should revert to the original method after each spec" do
-    StubbableClass.find(1).should equal(:original_return)
-  end
-
-  it "can stub! and mock the same message" do
-    StubbableClass.stub!(:msg).and_return(:stub_value)
-    StubbableClass.should_receive(:msg).with(:arg).and_return(:mock_value)
-
-    StubbableClass.msg.should equal(:stub_value)
-    StubbableClass.msg(:other_arg).should equal(:stub_value)
-    StubbableClass.msg(:arg).should equal(:mock_value)
-    StubbableClass.msg(:another_arg).should equal(:stub_value)
-    StubbableClass.msg(:yet_another_arg).should equal(:stub_value)
-    StubbableClass.msg.should equal(:stub_value)
-  end
-end
-
-describe "A mock" do
-  it "can stub!" do
-    mock = mock("stubbing mock")
-    mock.stub!(:msg).and_return(:value)
-    (1..10).each {mock.msg.should equal(:value)}
-  end
-  
-  it "can stub! and mock" do
-    mock = mock("stubbing mock")
-    mock.stub!(:stub_message).and_return(:stub_value)
-    mock.should_receive(:mock_message).once.and_return(:mock_value)
-    (1..10).each {mock.stub_message.should equal(:stub_value)}
-    mock.mock_message.should equal(:mock_value)
-    (1..10).each {mock.stub_message.should equal(:stub_value)}
-  end
-  
-  it "can stub! and mock the same message" do
-    mock = mock("stubbing mock")
-    mock.stub!(:msg).and_return(:stub_value)
-    mock.should_receive(:msg).with(:arg).and_return(:mock_value)
-    mock.msg.should equal(:stub_value)
-    mock.msg(:other_arg).should equal(:stub_value)
-    mock.msg(:arg).should equal(:mock_value)
-    mock.msg(:another_arg).should equal(:stub_value)
-    mock.msg(:yet_another_arg).should equal(:stub_value)
-    mock.msg.should equal(:stub_value)
-  end
-end
-
-    

data/vendor/plugins/rspec/examples/passing/yielding_example.rb

@@ -1,33 +0,0 @@
-require File.dirname(__FILE__) + '/spec_helper'
-
-class MessageAppender
-  
-  def initialize(appendage)
-    @appendage = appendage
-  end
-  
-  def append_to(message)
-    if_told_to_yield do
-      message << @appendage
-    end
-  end
-    
-end
-
-describe "a message expectation yielding to a block" do
-  it "should yield if told to" do
-    appender = MessageAppender.new("appended to")
-    appender.should_receive(:if_told_to_yield).and_yield
-    message = ""
-    appender.append_to(message)
-    message.should == "appended to"
-  end
-
-  it "should not yield if not told to" do
-    appender = MessageAppender.new("appended to")
-    appender.should_receive(:if_told_to_yield)
-    message = ""
-    appender.append_to(message)
-    message.should == ""
-  end
-end

data/vendor/plugins/rspec/features/before_and_after_blocks/before_and_after_blocks.feature

@@ -1,168 +0,0 @@
-Feature: before and after blocks
-
-  As a developer using RSpec
-  I want to execute arbitrary code before and after each example
-  So that I can control the environment in which it is run
-  
-    This is supported by the before and after methods which each take a symbol
-    indicating the scope, and a block of code to execute.
-  
-    before(:each) blocks are run before each example
-    before(:all) blocks are run once before all of the examples in a group
-    before(:suite) blocks are run once before the entire suite
-
-    after(:each) blocks are run after each example
-    after(:all) blocks are run once after all of the examples in a group
-    after(:suite) blocks are run once after the entire suite
-
-    Before and after blocks are called in the following order:
-      before suite
-      before all
-      before each
-      after each
-      after all
-      after suite
-    
-    Before and after blocks can be defined in the example groups to which they
-    apply or in a configuration. When defined in a configuration, they can be
-    applied to all groups or subsets of all groups defined by example group
-    types.
-  
-  Scenario: define before(:each) block in example group
-    Given the following spec:
-      """
-      class Thing
-        def widgets
-          @widgets ||= []
-        end
-      end
-
-      describe Thing do
-        before(:each) do
-          @thing = Thing.new
-        end
-        
-        context "initialized in before(:each)" do
-          it "has 0 widgets" do
-            @thing.should have(0).widgets
-          end
-        
-          it "can get accept new widgets" do
-            @thing.widgets << Object.new
-          end
-        
-          it "does not share state across examples" do
-            @thing.should have(0).widgets
-          end
-        end
-      end
-      """
-  	When I run it with the spec script
-    Then the stdout should match "3 examples, 0 failures"
-  
-  Scenario: define before(:all) block in example group
-    Given the following spec:
-      """
-      class Thing
-        def widgets
-          @widgets ||= []
-        end
-      end
-
-      describe Thing do
-        before(:all) do
-          @thing = Thing.new
-        end
-        
-        context "initialized in before(:all)" do
-          it "has 0 widgets" do
-            @thing.should have(0).widgets
-          end
-        
-          it "can get accept new widgets" do
-            @thing.widgets << Object.new
-          end
-        
-          it "shares state across examples" do
-            @thing.should have(1).widgets
-          end
-        end
-      end
-      """
-  	When I run it with the spec script
-    Then the stdout should match "3 examples, 0 failures"
-  
-  Scenario: define before and after blocks in configuration
-    Given the following spec:
-      """
-      Spec::Runner.configure do |config|
-        config.before(:suite) do
-          $before_suite = "before suite"
-        end
-        config.before(:each) do
-          @before_each = "before each"
-        end
-        config.before(:all) do
-          @before_all = "before all"
-        end
-      end
-
-      describe "stuff in before blocks" do
-        describe "with :suite" do
-          it "should be available in the example" do
-            $before_suite.should == "before suite"
-          end
-        end
-        describe "with :all" do
-          it "should be available in the example" do
-            @before_all.should == "before all"
-          end
-        end
-        describe "with :each" do
-          it "should be available in the example" do
-            @before_each.should == "before each"
-          end
-        end
-      end
-      """
-    When I run it with the spec script
-    Then the stdout should match "3 examples, 0 failures"
-
-  Scenario: before/after blocks are run in order
-    Given the following spec:
-      """
-      Spec::Runner.configure do |config|
-        config.before(:suite) do
-          puts "before suite"
-        end
-        config.after(:suite) do
-          puts "after suite"
-        end
-      end
-
-      describe "before and after callbacks" do
-        before(:all) do
-          puts "before all"
-        end
-
-        before(:each) do
-          puts "before each"
-        end
-
-        after(:each) do
-          puts "after each"
-        end
-
-        after(:all) do
-          puts "after all"
-        end
-
-        it "gets run in order" do
-
-        end
-      end
-      """
-
-    When I run it with the spec script
-    Then the stdout should match /before suite\nbefore all\nbefore each\nafter each\n\.after all\n.*after suite/m
-

data/vendor/plugins/rspec/features/example_groups/autogenerated_docstrings.feature

@@ -1,45 +0,0 @@
-Feature: autogenerated docstrings
-
-  As an RSpec user
-  I want examples to generate their own names
-  So that I can reduce duplication between example names and example code
-
-  Scenario: run passing examples with ruby
-    Given the file ../../examples/passing/autogenerated_docstrings_example.rb
-
-    When I run it with the ruby interpreter -fs
-
-    Then the stdout should match /should equal 5/
-    And the stdout should match /should be < 5/
-    And the stdout should match /should include "a"/
-    And the stdout should match /should respond to #size/
-
-  Scenario: run failing examples with ruby
-    Given the file ../../examples/failing/failing_autogenerated_docstrings_example.rb
-
-    When I run it with the ruby interpreter -fs
-
-    Then the stdout should match /should equal 2/
-    And the stdout should match /should be > 5/
-    And the stdout should match /should include "b"/
-    And the stdout should match /should not respond to #size/
-
-  Scenario: run passing examples with spec
-    Given the file ../../examples/passing/autogenerated_docstrings_example.rb
-
-    When I run it with the spec script -fs
-
-    Then the stdout should match /should equal 5/
-    And the stdout should match /should be < 5/
-    And the stdout should match /should include "a"/
-    And the stdout should match /should respond to #size/
-
-  Scenario: run failing examples with spec
-    Given the file ../../examples/failing/failing_autogenerated_docstrings_example.rb
-
-    When I run it with the spec script -fs
-
-    Then the stdout should match /should equal 2/
-    And the stdout should match /should be > 5/
-    And the stdout should match /should include "b"/
-    And the stdout should match /should not respond to #size/

data/vendor/plugins/rspec/features/example_groups/example_group_with_should_methods.feature

@@ -1,17 +0,0 @@
-Feature: Spec::ExampleGroup with should methods
-
-  As an RSpec adopter accustomed to classes and methods
-  I want to use should_* methods in an ExampleGroup
-  So that I use RSpec with classes and methods that look more like RSpec examples
-
-  Scenario: Run with ruby
-    Given the file ../../resources/spec/example_group_with_should_methods.rb
-    When I run it with the ruby interpreter
-    Then the exit code should be 256
-    And the stdout should match "2 examples, 1 failure"
-
-  Scenario: Run with spec
-  Given the file ../../resources/spec/example_group_with_should_methods.rb
-    When I run it with the spec script
-    Then the exit code should be 256
-    And the stdout should match "2 examples, 1 failure"

data/vendor/plugins/rspec/features/example_groups/nested_groups.feature

@@ -1,17 +0,0 @@
-Feature: Nested example groups
-
-  As an RSpec user
-  I want to nest examples groups
-  So that I can better organize my examples
-
-  Scenario: Run with ruby
-    Given the file ../../examples/passing/stack_spec_with_nested_example_groups.rb
-    When I run it with the ruby interpreter -fs
-    Then the stdout should match /Stack \(empty\)/
-    And the stdout should match /Stack \(full\)/
-
-  Scenario: Run with spec
-    Given the file ../../examples/passing/stack_spec_with_nested_example_groups.rb
-    When I run it with the spec script -fs
-    Then the stdout should match /Stack \(empty\)/
-    And the stdout should match /Stack \(full\)/

data/vendor/plugins/rspec/features/example_groups/output.feature

@@ -1,20 +0,0 @@
-Feature: Getting correct output
-
-  As an RSpec user
-  I want to see output only once
-  So that I don't get confused
-
-  Scenario: Run with ruby
-    Given the file ../../resources/spec/simple_spec.rb
-    When I run it with the ruby interpreter
-    Then the exit code should be 0
-    And the stdout should not match /\d+ tests, \d+ assertions, \d+ failures, \d+ errors/m
-    And the stdout should match "1 example, 0 failures"
-
-  Scenario: Run with CommandLine object
-    Given the file ../../resources/spec/simple_spec.rb
-    When I run it with the CommandLine object
-    Then the exit code should be 0
-    And the stdout should not match "Loaded suite"
-    And the stdout should not match /\d+ tests, \d+ assertions, \d+ failures, \d+ errors/m
-    And the stdout should match "1 example, 0 failures"

data/vendor/plugins/rspec/features/interop/examples_and_tests_together.feature

@@ -1,31 +0,0 @@
-Feature: Spec and test together
-
-  As an RSpec adopter with existing Test::Unit tests
-  I want to run a few specs alongside my existing Test::Unit tests
-  So that I can experience a smooth, gradual migration path
-
-  Scenario: Run with ruby
-    Given the file ../../resources/test/spec_and_test_together.rb
-
-    When I run it with the ruby interpreter -fs
-
-    Then the exit code should be 256
-    And the stdout should match "ATest"
-    And the stdout should match "Test::Unit::AssertionFailedError in 'An Example should fail with assert'"
-    And the stdout should match "'An Example should fail with should' FAILED"
-    And the stdout should match "10 examples, 6 failures"
-    And the stdout should match /expected: 40,\s*got: 4/m
-    And the stdout should match /expected: 50,\s*got: 5/m
-    
-  Scenario: Run with spec
-    Given the file ../../resources/test/spec_and_test_together.rb
-
-    When I run it with the spec script -fs
-
-    Then the exit code should be 256
-    And the stdout should match "ATest"
-    And the stdout should match "Test::Unit::AssertionFailedError in 'An Example should fail with assert'"
-    And the stdout should match "'An Example should fail with should' FAILED"
-    And the stdout should match "10 examples, 6 failures"
-    And the stdout should match /expected: 40,\s*got: 4/m
-    And the stdout should match /expected: 50,\s*got: 5/m

data/vendor/plugins/rspec/features/interop/test_but_not_test_unit.feature

@@ -1,14 +0,0 @@
-Story: Test is defined, but not Test::Unit
-
-  As an RSpec user who has my own library named Test (but not Test::Unit)
-  I want to run examples without getting Test::Unit NameErrors
-
-  Scenario: Run with ruby
-    Given the file ../../resources/test/spec_including_test_but_not_unit.rb
-    When I run it with the ruby interpreter
-    Then the stderr should not match "Test::Unit"
-
-  Scenario: Run with spec
-    Given the file ../../resources/test/spec_including_test_but_not_unit.rb
-    When I run it with the spec script
-    Then the stderr should not match "Test::Unit"

data/vendor/plugins/rspec/features/interop/test_case_with_should_methods.feature

@@ -1,17 +0,0 @@
-Story: Test::Unit::TestCase extended by rspec with should methods
-
-  As an RSpec adopter with existing Test::Unit tests
-  I want to use should_* methods in a Test::Unit::TestCase
-  So that I use RSpec with classes and methods that look more like RSpec examples
-
-  Scenario: Run with ruby
-    Given the file ../../resources/test/test_case_with_should_methods.rb
-    When I run it with the ruby interpreter
-    Then the exit code should be 256
-    And the stdout should match "5 examples, 3 failures"
-
-  Scenario: Run with spec
-    Given the file ../../resources/test/test_case_with_should_methods.rb
-    When I run it with the spec script
-    Then the exit code should be 256
-    And the stdout should match "5 examples, 3 failures"

data/vendor/plugins/rspec/features/mock_framework_integration/use_flexmock.feature

@@ -1,9 +0,0 @@
-Story: Getting correct output with flexmock
-
-  As an RSpec user who prefers flexmock
-  I want to be able to use flexmock without rspec mocks interfering
-
-  Scenario: Mock with flexmock
-    Given the file ../../resources/spec/spec_with_flexmock.rb
-    When I run it with the ruby interpreter
-    Then the exit code should be 0