nutshell-crm 0.0.1

data/vendor/bundle/gems/rspec-core-2.7.1/features/configuration/fail_fast.feature

@@ -0,0 +1,77 @@
+Feature: fail fast
+
+  Use the fail_fast option to tell RSpec to abort the run on first failure:
+
+      RSpec.configure {|c| c.fail_fast = true}
+
+  Background:
+    Given a file named "spec/spec_helper.rb" with:
+      """
+      RSpec.configure {|c| c.fail_fast = true}
+      """
+
+  Scenario: fail_fast with no failures (runs all examples)
+    Given a file named "spec/example_spec.rb" with:
+      """
+      describe "something" do
+        it "passes" do
+        end
+
+        it "passes too" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb`
+    Then the examples should all pass
+
+  Scenario: fail_fast with first example failing (only runs the one example)
+    Given a file named "spec/example_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "fails" do
+          fail
+        end
+
+        it "passes" do
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb -fd`
+    Then the output should contain "1 example, 1 failure"
+
+  Scenario: fail_fast with multiple files, second example failing (only runs the first two examples)
+    Given a file named "spec/example_1_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+
+        it "fails" do
+          fail
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    And a file named "spec/example_2_spec.rb" with:
+      """
+      require "spec_helper"
+      describe "something" do
+        it "passes" do
+        end
+      end
+
+      describe "something else" do
+        it "fails" do
+          fail
+        end
+      end
+      """
+    When I run `rspec spec`
+    Then the output should contain "2 examples, 1 failure"

data/vendor/bundle/gems/rspec-core-2.7.1/features/configuration/read_options_from_file.feature

@@ -0,0 +1,87 @@
+Feature: read command line configuration options from files
+
+  RSpec reads command line configuration options from files in two different
+  locations:
+  
+    Local:  "./.rspec" (i.e. in the project's root directory)
+    Global: "~/.rspec" (i.e. in the user's home directory)
+
+  Options declared in the local file override those in the global file, while
+  those declared in RSpec.configure will override any ".rspec" file.
+
+  Scenario: color set in .rspec
+    Given a file named ".rspec" with:
+      """
+      --color
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "color_enabled" do
+        context "when set with RSpec.configure" do
+          before do
+            # color is disabled for non-tty output, so stub the output stream
+            # to say it is tty, even though we're running this with cucumber
+            RSpec.configuration.output_stream.stub(:tty?) { true }
+          end
+
+          it "is true" do
+            RSpec.configuration.should be_color_enabled
+          end
+        end
+      end
+      """
+    When I run `rspec ./spec/example_spec.rb`
+    Then the examples should all pass
+
+  Scenario: custom options file
+    Given a file named "my.options" with:
+      """
+      --format documentation
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "formatter set in custom options file" do
+        it "sets formatter" do
+          RSpec.configuration.formatters.first.
+            should be_a(RSpec::Core::Formatters::DocumentationFormatter)
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb --options my.options`
+    Then the examples should all pass
+
+  Scenario: RSpec ignores ./.rspec when custom options file is used
+    Given a file named "my.options" with:
+      """
+      --format documentation
+      """
+    And a file named ".rspec" with:
+      """
+      --color
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "custom options file" do
+        it "causes .rspec to be ignored" do
+          RSpec.configuration.color_enabled.should be_false
+        end
+      end
+      """
+    When I run `rspec spec/example_spec.rb --options my.options`
+    Then the examples should all pass
+
+  Scenario: using ERB in .rspec
+    Given a file named ".rspec" with:
+      """
+      --format <%= true ? 'documentation' : 'progress' %>
+      """
+    And a file named "spec/example_spec.rb" with:
+      """
+      describe "formatter" do
+        it "is set to documentation" do
+          RSpec.configuration.formatters.first.should be_an(RSpec::Core::Formatters::DocumentationFormatter)
+        end
+      end
+      """
+    When I run `rspec ./spec/example_spec.rb`
+    Then the examples should all pass

data/vendor/bundle/gems/rspec-core-2.7.1/features/example_groups/basic_structure.feature

@@ -0,0 +1,55 @@
+Feature: basic structure (describe/it)
+
+  RSpec is a DSL for creating executable examples of how code is expected to
+  behave, organized in groups. It uses the words "describe" and "it" so we can
+  express concepts like a conversation:
+
+      "Describe an account when it is first opened."
+      "It has a balance of zero."
+
+  The `describe` method creates an example group.  Within the block passed to
+  `describe` you can declare nested groups using the `describe` or `context`
+  methods, or you can declare examples using the `it` or `specify` methods.
+
+  Under the hood, an example group is a class in which the block passed to
+  `describe` or `context` is evaluated. The blocks passed to `it` are evaluated
+  in the context of an _instance_ of that class.
+  
+  Scenario: one group, one example
+    Given a file named "sample_spec.rb" with:
+    """
+    describe "something" do
+      it "does something" do
+      end
+    end
+    """
+    When I run `rspec sample_spec.rb -fn`
+    Then the output should contain:
+      """
+      something
+        does something
+      """
+
+  Scenario: nested example groups (using context)
+    Given a file named "nested_example_groups_spec.rb" with:
+    """
+    describe "something" do
+      context "in one context" do
+        it "does one thing" do
+        end
+      end
+      context "in another context" do
+        it "does another thing" do
+        end
+      end
+    end
+    """
+    When I run `rspec nested_example_groups_spec.rb -fdoc`
+    Then the output should contain:
+      """
+      something
+        in one context
+          does one thing
+        in another context
+          does another thing
+      """

data/vendor/bundle/gems/rspec-core-2.7.1/features/example_groups/shared_context.feature

@@ -0,0 +1,74 @@
+Feature: shared context
+
+  Use `shared_context` to define a block that will be evaluated in the context
+  of example groups either explicitly, using `include_context`, or implicitly by
+  matching metadata.
+
+  Background:
+    Given a file named "shared_stuff.rb" with:
+      """
+      shared_context "shared stuff", :a => :b do
+        before { @some_var = :some_value }
+        def shared_method
+          "it works"
+        end
+        let(:shared_let) { {'arbitrary' => 'object'} }
+        subject do
+          'this is the subject'
+        end
+      end
+      """
+  
+  Scenario: declare shared context and include it with include_context
+    Given a file named "shared_context_example.rb" with:
+      """
+      require "./shared_stuff.rb"
+
+      describe "group that includes a shared context using 'include_context'" do
+        include_context "shared stuff"
+
+        it "has access to methods defined in shared context" do
+          shared_method.should eq("it works")
+        end
+
+        it "has access to methods defined with let in shared context" do
+          shared_let['arbitrary'].should eq('object')
+        end
+
+        it "runs the before hooks defined in the shared context" do
+          @some_var.should be(:some_value)
+        end
+
+        it "accesses the subject defined in the shared context" do
+          subject.should eq('this is the subject')
+        end
+      end
+      """
+    When I run `rspec shared_context_example.rb`
+    Then the examples should all pass
+
+  Scenario: declare shared context and include it with metadata
+    Given a file named "shared_context_example.rb" with:
+      """
+      require "./shared_stuff.rb"
+
+      describe "group that includes a shared context using metadata", :a => :b do
+        it "has access to methods defined in shared context" do
+          shared_method.should eq("it works")
+        end
+
+        it "has access to methods defined with let in shared context" do
+          shared_let['arbitrary'].should eq('object')
+        end
+
+        it "runs the before hooks defined in the shared context" do
+          @some_var.should be(:some_value)
+        end
+
+        it "accesses the subject defined in the shared context" do
+          subject.should eq('this is the subject')
+        end
+      end
+      """
+    When I run `rspec shared_context_example.rb`
+    Then the examples should all pass

data/vendor/bundle/gems/rspec-core-2.7.1/features/example_groups/shared_examples.feature

@@ -0,0 +1,204 @@
+Feature: shared examples
+
+  Shared examples let you describe behaviour of types or modules. When
+  declared, a shared group's content is stored. It is only realized in the
+  context of another example group, which provides any context the shared group
+  needs to run.
+
+  A shared group is included in another group using any of:
+  
+      include_examples "name"      # include the examples in the current context
+      it_behaves_like "name"       # include the examples in a nested context
+      it_should_behave_like "name" # include the examples in a nested context
+
+  WARNING: Files containing shared groups must be loaded before the files that
+  use them.  While there are conventions to handle this, RSpec does _not_ do
+  anything special (like autoload). Doing so would require a strict naming
+  convention for files that would break existing suites.
+
+  CONVENTIONS:
+
+  1.  The simplest approach is to require files with shared examples explicitly
+      from the files that use them. Keep in mind that RSpec adds the `spec`
+      directory to the `LOAD_PATH`, so you can say `require
+      'shared_examples_for_widgets'` to require a file at
+      `#{PROJECT_ROOT}/spec/shared_examples_for_widgets.rb`.
+
+  2.  Put files containing shared examples in `spec/support/` and require files
+      in that directory from `spec/spec_helper.rb`:
+
+          Dir["spec/support/**/*.rb"].each {|f| require f}
+
+      This is included in the generated `spec/spec_helper.rb` file in
+      `rspec-rails`
+
+  3. When all of the groups that include the shared group, just declare
+     the shared group in the same file.
+
+  Scenario: shared examples group included in two groups in one file
+    Given a file named "collection_spec.rb" with:
+      """
+      require "set"
+
+      shared_examples "a collection" do
+        let(:collection) { described_class.new([7, 2, 4]) }
+
+        context "initialized with 3 items" do
+          it "says it has three items" do
+            collection.size.should eq(3)
+          end
+        end
+
+        describe "#include?" do
+          context "with an an item that is in the collection" do
+            it "returns true" do
+              collection.include?(7).should be_true
+            end
+          end
+
+          context "with an an item that is not in the collection" do
+            it "returns false" do
+              collection.include?(9).should be_false
+            end
+          end
+        end
+      end
+
+      describe Array do
+        it_behaves_like "a collection"
+      end
+
+      describe Set do
+        it_behaves_like "a collection"
+      end
+      """
+    When I run `rspec collection_spec.rb --format documentation`
+    Then the examples should all pass
+    And the output should contain:
+      """
+      Array
+        behaves like a collection
+          initialized with 3 items
+            says it has three items
+          #include?
+            with an an item that is in the collection
+              returns true
+            with an an item that is not in the collection
+              returns false
+
+      Set
+        behaves like a collection
+          initialized with 3 items
+            says it has three items
+          #include?
+            with an an item that is in the collection
+              returns true
+            with an an item that is not in the collection
+              returns false
+      """
+
+  Scenario: Providing context to a shared group using a block
+    Given a file named "shared_example_group_spec.rb" with:
+    """
+    require "set"
+
+    shared_examples "a collection object" do
+      describe "<<" do
+        it "adds objects to the end of the collection" do
+          collection << 1
+          collection << 2
+          collection.to_a.should eq([1,2])
+        end
+      end
+    end
+
+    describe Array do
+      it_behaves_like "a collection object" do
+        let(:collection) { Array.new }
+      end
+    end
+
+    describe Set do
+      it_behaves_like "a collection object" do
+        let(:collection) { Set.new }
+      end
+    end
+    """
+    When I run `rspec shared_example_group_spec.rb --format documentation`
+    Then the examples should all pass
+    And the output should contain:
+      """
+      Array
+        behaves like a collection object
+          <<
+            adds objects to the end of the collection
+
+      Set
+        behaves like a collection object
+          <<
+            adds objects to the end of the collection
+      """
+
+  Scenario: Passing parameters to a shared example group
+    Given a file named "shared_example_group_params_spec.rb" with:
+    """
+    shared_examples "a measurable object" do |measurement, measurement_methods|
+      measurement_methods.each do |measurement_method|
+        it "should return #{measurement} from ##{measurement_method}" do
+          subject.send(measurement_method).should == measurement
+        end
+      end
+    end
+
+    describe Array, "with 3 items" do
+      subject { [1, 2, 3] }
+      it_should_behave_like "a measurable object", 3, [:size, :length]
+    end
+
+    describe String, "of 6 characters" do
+      subject { "FooBar" }
+      it_should_behave_like "a measurable object", 6, [:size, :length]
+    end
+    """
+    When I run `rspec shared_example_group_params_spec.rb --format documentation`
+    Then the examples should all pass
+    And the output should contain:
+      """
+      Array with 3 items
+        it should behave like a measurable object
+          should return 3 from #size
+          should return 3 from #length
+
+      String of 6 characters
+        it should behave like a measurable object
+          should return 6 from #size
+          should return 6 from #length
+      """
+
+  Scenario: Aliasing "it_should_behave_like" to "it_has_behavior"
+    Given a file named "shared_example_group_spec.rb" with:
+      """
+      RSpec.configure do |c|
+        c.alias_it_should_behave_like_to :it_has_behavior, 'has behavior:'
+      end
+
+      shared_examples 'sortability' do
+        it 'responds to <=>' do
+          sortable.should respond_to(:<=>)
+        end
+      end
+
+      describe String do
+        it_has_behavior 'sortability' do
+          let(:sortable) { 'sample string' }
+        end
+      end
+      """
+    When I run `rspec shared_example_group_spec.rb --format documentation`
+    Then the examples should all pass
+    And the output should contain:
+      """
+      String
+        has behavior: sortability
+          responds to <=>
+      """