rspec-rails 2.13.1 → 2.13.2

data/features/model_specs/transactional_examples.feature

@@ -1,109 +0,0 @@
-Feature: transactional examples
-
-  By default rspec executes each individual example in a transaction.
-
-  You can also explicitly enable/disable transactions the configuration
-  property 'use_transactional_examples'.
-
-  Scenario: run in transactions (default)
-    Given a file named "spec/models/widget_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe Widget do
-        it "has none to begin with" do
-          expect(Widget.count).to eq 0
-        end
-
-        it "has one after adding one" do
-          Widget.create
-          expect(Widget.count).to eq 1
-        end
-
-        it "has none after one was created in a previous example" do
-          expect(Widget.count).to eq 0
-        end
-      end
-      """
-    When I run `rspec spec/models/widget_spec.rb`
-    Then the examples should all pass
-
-  Scenario: run in transactions (explicit)
-    Given a file named "spec/models/widget_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      RSpec.configure do |c|
-        c.use_transactional_examples = true
-      end
-
-      describe Widget do
-        it "has none to begin with" do
-          expect(Widget.count).to eq 0
-        end
-
-        it "has one after adding one" do
-          Widget.create
-          expect(Widget.count).to eq 1
-        end
-
-        it "has none after one was created in a previous example" do
-          expect(Widget.count).to eq 0
-        end
-      end
-      """
-    When I run `rspec spec/models/widget_spec.rb`
-    Then the examples should all pass
-
-  Scenario: disable transactions (explicit)
-    Given a file named "spec/models/widget_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      RSpec.configure do |c|
-        c.use_transactional_examples = false
-        c.order = "default"
-      end
-
-      describe Widget do
-        it "has none to begin with" do
-          expect(Widget.count).to eq 0
-        end
-
-        it "has one after adding one" do
-          Widget.create
-          expect(Widget.count).to eq 1
-        end
-
-        it "has one after one was created in a previous example" do
-          expect(Widget.count).to eq 1
-        end
-
-        after(:all) { Widget.destroy_all }
-      end
-      """
-    When I run `rspec spec/models/widget_spec.rb`
-    Then the examples should all pass
-
-  Scenario: run in transactions with fixture
-    Given a file named "spec/models/thing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe Thing do
-        fixtures :things
-        it "fixture method defined" do
-          things(:one)
-        end
-      end
-      """
-    Given a file named "spec/fixtures/things.yml" with:
-      """
-      one:
-        name: MyString
-      """
-    When I run `rspec spec/models/thing_spec.rb`
-    Then the examples should all pass
-
-
-

data/features/request_specs/request_spec.feature

@@ -1,49 +0,0 @@
-Feature: request spec
-
-  Request specs provide a thin wrapper around Rails' integration tests, and are
-  designed to drive behavior through the full stack, including routing
-  (provided by Rails) and without stubbing (that's up to you).
-
-  With request specs, you can:
-
-  * specify a single request
-  * specify multiple requests across multiple controllers
-  * specify multiple requests across multiple sessions
-
-  Check the rails documentation on integration tests for more information.
-
-  RSpec provides two matchers that delegate to Rails assertions:
-
-      render_template # delegates to assert_template
-      redirect_to     # delegates to assert_redirected_to
-
-  Check the Rails docs for details on these methods as well.
-
-  [Capybara](http://github.com/jnicklas/capybara) is no longer supported in
-  request specs as of Capybara 2.0.0. The recommended way to use Capybara is
-  with [feature specs](../feature-specs/feature-spec).
-
-  Scenario: specify managing a Widget with Rails integration methods
-    Given a file named "spec/requests/widget_management_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "Widget management" do
-
-        it "creates a Widget and redirects to the Widget's page" do
-          get "/widgets/new"
-          expect(response).to render_template(:new)
-
-          post "/widgets", :widget => {:name => "My Widget"}
-
-          expect(response).to redirect_to(assigns(:widget))
-          follow_redirect!
-
-          expect(response).to render_template(:show)
-          expect(response.body).to include("Widget was successfully created.")
-        end
-
-      end
-      """
-    When I run `rspec spec/requests/widget_management_spec.rb`
-    Then the example should pass

data/features/routing_specs/README.md

@@ -1,16 +0,0 @@
-Routing specs live in the `spec/routing` directory, or any example group with
-`:type => :routing`.
-
-Simple apps with nothing but standard RESTful routes won't get much value from
-routing specs, but they can provide significant value when used to specify
-customized routes, like vanity links, slugs, etc.
-
-    expect(:get => "/articles/2012/11/when-to-use-routing-specs").to route_to(
-      :controller => "articles",
-      :month => "2012-11",
-      :slug => "when-to-use-routing-specs"
-    )
-
-They are also valuable for routes that should not be available:
-
-    expect(:delete => "/accounts/37").not_to be_routable

data/features/routing_specs/be_routable_matcher.feature

@@ -1,80 +0,0 @@
-Feature: be_routable matcher
-
-  The `be_routable` matcher is best used with `should_not` to specify that a
-  given route should not be routable. It is available in routing specs (in
-  spec/routing) and controller specs (in spec/controllers).
-
-  Scenario: specify routeable route should not be routable (fails)
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "does not route to widgets" do
-          expect(:get => "/widgets").not_to be_routable
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the output should contain "1 example, 1 failure"
-
-  Scenario: specify non-routeable route should not be routable (passes)
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "does not route to widgets/foo/bar" do
-          expect(:get => "/widgets/foo/bar").not_to be_routable
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the examples should all pass
-
-  Scenario: specify routeable route should be routable (passes)
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes to /widgets" do
-          expect(:get => "/widgets").to be_routable
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the examples should all pass
-
-  Scenario: specify non-routeable route should be routable (fails)
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes to widgets/foo/bar" do
-          expect(:get => "/widgets/foo/bar").to be_routable
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the output should contain "1 example, 1 failure"
-
-  Scenario: be_routable in a controller spec
-    Given a file named "spec/controllers/widgets_controller_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe WidgetsController do
-        it "routes to /widgets" do
-          expect(:get => "/widgets").to be_routable
-        end
-      end
-      """
-
-    When I run `rspec spec/controllers/widgets_controller_spec.rb`
-    Then the examples should all pass

data/features/routing_specs/engine_routes.feature

@@ -1,38 +0,0 @@
-Feature: engine routes
-
-  Routing specs can specify the routeset that will be used for the example
-  group. This is most useful when testing Rails engines.
-
-  @unsupported-on-rails-3-0
-  Scenario: specify engine route
-    Given a file named "spec/routing/engine_routes_spec.rb" with:
-    """ruby
-    require "spec_helper"
-
-    # A very simple Rails engine
-    module MyEngine
-      class Engine < ::Rails::Engine
-        isolate_namespace MyEngine
-      end
-
-      Engine.routes.draw do
-        resources :widgets, :only => [:index]
-      end
-
-      class WidgetsController < ::ActionController::Base
-        def index
-        end
-      end
-    end
-
-    describe MyEngine::WidgetsController do
-      routes { MyEngine::Engine.routes }
-
-      it "routes to the list of all widgets" do
-        expect(:get => widgets_path).
-          to route_to(:controller => "my_engine/widgets", :action => "index")
-      end
-    end
-    """
-    When I run `rspec spec`
-    Then the examples should all pass

data/features/routing_specs/named_routes.feature

@@ -1,18 +0,0 @@
-Feature: named routes
-
-  Routing specs have access to named routes.
-
-  Scenario: access named route
-    Given a file named "spec/routing/widget_routes_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes to the widgets controller" do
-        it "routes a named route" do
-          expect(:get => new_widget_path).
-            to route_to(:controller => "widgets", :action => "new")
-        end
-      end
-      """
-    When I run `rspec spec`
-    Then the examples should all pass

data/features/routing_specs/route_to_matcher.feature

@@ -1,90 +0,0 @@
-Feature: route_to matcher
-
-  The `route_to` matcher specifies that a request (verb + path) is routable.
-  It is most valuable when specifying routes other than standard RESTful
-  routes.
-
-      expect(get("/")).to route_to("welcome#index") # new in 2.6.0
-
-      or
-
-      expect(:get => "/").to route_to(:controller => "welcome")
-
-  Scenario: passing route spec with shortcut syntax
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes /widgets to the widgets controller" do
-          expect(get("/widgets")).
-            to route_to("widgets#index")
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the examples should all pass
-
-  Scenario: passing route spec with verbose syntax
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes /widgets to the widgets controller" do
-          expect(:get => "/widgets").
-            to route_to(:controller => "widgets", :action => "index")
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the examples should all pass
-
-  Scenario: route spec for a route that doesn't exist (fails)
-    Given a file named "spec/routing/widgets_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes /widgets/foo to the /foo action" do
-          expect(get("/widgets/foo")).to route_to("widgets#foo")
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/widgets_routing_spec.rb`
-    Then the output should contain "1 failure"
-
-  Scenario: route spec for a namespaced route with shortcut specifier
-    Given a file named "spec/routing/admin_routing_spec.rb" with:
-      """ruby
-      require "spec_helper"
-
-      describe "routes for Widgets" do
-        it "routes /admin/accounts to the admin/accounts controller" do
-          expect(get("/admin/accounts")).
-            to route_to("admin/accounts#index")
-        end
-      end
-      """
-
-    When I run `rspec spec/routing/admin_routing_spec.rb`
-    Then the examples should all pass
-
-  Scenario: route spec for a namespaced route with verbose specifier
-   Given a file named "spec/routing/admin_routing_spec.rb" with:
-     """ruby
-     require "spec_helper"
-
-     describe "routes for Widgets" do
-       it "routes /admin/accounts to the admin/accounts controller" do
-         expect(get("/admin/accounts")).
-           to route_to(:controller => "admin/accounts", :action => "index")
-       end
-     end
-     """
-
-   When I run `rspec spec/routing/admin_routing_spec.rb`
-   Then the examples should all pass

data/features/step_definitions/additional_cli_steps.rb

@@ -1,4 +0,0 @@
-Then /^the example(s)? should( all)? pass$/ do |_, _|
-  step %q{the output should contain "0 failures"}
-  step %q{the exit status should be 0}
-end

data/features/step_definitions/model_steps.rb

@@ -1,3 +0,0 @@
-Given /a (\w+) model/ do |model_class_name|
-  puts eval(model_class_name)
-end

data/features/support/env.rb

@@ -1,53 +0,0 @@
-require 'aruba/cucumber'
-
-module ArubaExt
-  def run(cmd)
-    super(cmd =~ /^rspec/ ? "bin/#{cmd}" : cmd)
-  end
-end
-
-World(ArubaExt)
-
-Before do
-  @aruba_timeout_seconds = 30
-end
-
-unless File.directory?('./tmp/example_app')
-  system "rake generate:app generate:stuff"
-end
-
-def aruba_path(file_or_dir)
-  File.expand_path("../../../#{file_or_dir.sub('example_app','aruba')}", __FILE__)
-end
-
-def example_app_path(file_or_dir)
-  File.expand_path("../../../#{file_or_dir}", __FILE__)
-end
-
-def write_symlink(file_or_dir)
-  source = example_app_path(file_or_dir)
-  target = aruba_path(file_or_dir)
-  system "ln -s #{source} #{target}"
-end
-
-def copy(file_or_dir)
-  source = example_app_path(file_or_dir)
-  target = aruba_path(file_or_dir)
-  system "cp -r #{source} #{target}"
-end
-
-Before do
-  steps %Q{
-    Given a directory named "spec"
-  }
-
-  Dir['tmp/example_app/*'].each do |file_or_dir|
-    if !(file_or_dir =~ /spec$/)
-      write_symlink(file_or_dir)
-    end
-  end
-
-  ["spec/spec_helper.rb"].each do |file_or_dir|
-    write_symlink("tmp/example_app/#{file_or_dir}")
-  end
-end