minitest-spec-rails-orangejulius 5.0.3.pre.orangejulius

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: d87e7075302d785455b782511212e975fe042c5e
+  data.tar.gz: 9d175d652bb955068bb1d4ad2aa2ae5c15a36abc
+SHA512:
+  metadata.gz: 929f40dedfad705694a76a7e4147544b803ed80dfb5bc8d8b84f0e533921ab8057b569aab2ac3345d67daa1dfe8d04793be8d11cd2277c297fd8767087e62de7
+  data.tar.gz: d0076efa0c9ccf441b4139eb0beae061484c6e59e4f426ca73372f5aa69d28cd633fc65210dc6fb494853db6766b30d9db602b92d9a6caa609751497f6a79098

data/.gitignore

@@ -0,0 +1,7 @@
+*.gem
+.bundle
+.ruby-version
+gemfiles/*
+Gemfile.lock
+pkg/*
+*.log

data/.travis.yml

@@ -0,0 +1,12 @@
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - 2.1.1
+install:
+  - gem install bundler
+  - bundle --version
+  - bundle install
+before_script:
+  - bundle exec rake appraisal:setup
+script:
+  - bundle exec rake appraisal test

data/Appraisals

@@ -0,0 +1,3 @@
+
+appraise 'rails41' do
+end

data/CHANGELOG.md

@@ -0,0 +1,142 @@
+
+## 5.0.3
+
+* Fixed ActionView load order & url helpers. Fixes #42.
+
+
+## 5.0.2
+
+* Fixed initialization callbacks for latest Rails 4.1. Fixes #39.
+
+
+## 5.0.1
+
+* Change initialization so that ActiveSupport always comes first.
+
+
+## 5.0.0
+
+* Minitest 5.x and Rails 4.1 compatability. Fixes #36.
+* Fix nested described test names along with Minitest::Spec.describe_stack. Fixed #21.
+* Leverage `ActiveSupport::Testing::ConstantLookup` for our `described_class` interface.
+
+
+## 4.7.6
+
+* Fix nested described test names. Fixes #21.
+
+
+## 4.7.5
+
+* Fixed gemspec using '>= 3.0', '< 4.1'. Fixed #35.
+
+
+## 4.7.4
+
+* Enforces case sensitivity on registered spec types. Fixes #26.
+
+
+## 4.7.3
+
+* Allow using ActiveSupport's Declarative#test as an alias to it. Thanks @ysbaddaden. Fixes #23.
+
+
+## 4.7.2
+
+* Register non ActiveRecord::Base classes correctly. Thanks @mptre.
+
+
+## 4.7.1
+
+* Only use a TU shim for Ruby 1.8. See README for info. Fixes #18.
+
+
+## 4.7.0
+
+* Use Minitest::Spec::DSL provided by Minitest 4.7.
+
+
+## 4.3.8
+
+* Less coupling to ActiveRecord ORM, works for MongoDB now. Thanks @kimsuelim
+
+
+## v4.3.7
+
+* Fix helper test bug where calling methods in first context block blew up. Fixes #13.
+
+
+## v4.3.6
+
+* Only require the freedom patches and autorun when Rails.env.test?
+
+
+## v4.3.5
+
+* Make sure #described_class works in ActiveSupport::TestCase class level.
+
+
+## v4.3.4
+
+* Add mini_should support and talk about matchers.
+
+
+## v4.3.3
+
+* Fix MiniTest::Unit::TestCase hack for Rails 4, ignore in Rails 3.
+
+
+## v4.3.2
+
+* Way better support for controller_class, mailer_class, and helper_class reflection.
+
+
+## v4.3.1
+
+* Eager load controller_class, mailer_class, and helper_class.
+
+
+## v4.3.0
+
+* All new MiniTest::Spec for Rails!!! Tested to the hilt!!!
+* Track MiniTest's major/minior version number.
+
+
+## v3.0.7
+
+* Must use MiniTest version ~> 2.1. As 3.x will not work.
+
+
+## v3.0.6
+
+* Use #constantize vs. #safe_constantize for Rails 3.0 compatability.
+
+
+## v3.0.5
+
+* Use ActionController::IntegrationTest vs. ActionDispatch::IntegrationTest
+
+
+## v3.0.4
+
+* Use class app setter for integration tests.
+
+
+## v3.0.3
+
+* Stronger test case organization where we properly setup functional and integraiton tests
+  while also allowing an alternate pure MiniTest::Spec outter file describe block. [Jack Chu]
+
+
+## v3.0.2
+
+* Remove version deps on minitest since v3 is out. Should work with any v2/3 version.
+
+
+## v3.0.1
+
+* Add rails to the gemspec.
+
+## v3.0.0
+
+* Initial Release, targeted to Rails 3.x.

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+gemspec
+

data/MIT-LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2011 Ken Collins, <ken@metaskills.net>
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation
+files (the "Software"), to deal in the Software without
+restriction, including without limitation the rights to use,
+copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following
+conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
+OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
+HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
+WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
+OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,290 @@
+<img src="http://cdn.metaskills.net/minitest-spec-rails.png" width="233" height="154" />
+
+# Make Rails Use MiniTest::Spec!
+
+
+The minitest-spec-rails gem makes it easy to use the MiniTest::Spec DSL within your existing Rails 2.3, 3.x or 4.x test suite. It does this by forcing ActiveSupport::TestCase to utilize the MiniTest::Spec::DSL.
+
+[![Gem Version](https://badge.fury.io/rb/minitest-spec-rails.png)](http://badge.fury.io/rb/minitest-spec-rails)
+[![Build Status](https://secure.travis-ci.org/metaskills/minitest-spec-rails.png)](http://travis-ci.org/metaskills/minitest-spec-rails)
+[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/metaskills/minitest-spec-rails)
+
+
+## Usage
+
+Existing or new Rails applications that use the default Rails testing structure can simply drop in the minitest-spec-gem and start writing their tests in the new spec DSL. Since MiniTest::Spec is built on top of MiniTest::Unit, a replacement for Test::Unit, all of your existing tests will continue to work.
+
+
+#### Rails 4.1
+
+Our master branch is tracking rails master which is active development for Rails 4.1 which uses minitest 5.0.
+
+
+#### For Rails 3.x or 4.0
+
+Our [3-x-stable](https://github.com/metaskills/minitest-spec-rails/tree/3-x-stable) branch is meant for both Rails 3.x or 4.0 specifically. This version uses the latest 4.x series of minitest.
+
+```ruby
+group :test do
+  gem 'minitest-spec-rails'
+end
+```
+
+#### For Rails 2.3
+
+Our [2-3-stable](https://github.com/metaskills/minitest-spec-rails/tree/2-3-stable) branch tracks our 3.1 version number and is guaranteed to work on any Rails 2.3 version. Since Rails 2.3 does not have a configurable Railtie, we have enabled the [mini-shoulda](#mini_shoulda) option all the time. This means that if you are on Rails 2.3 under either Ruby 1.8 or 1.9, perhaps using Shoulda, you have a solid upgrade path! Get your tests running with minitest-spec-rails first and nothing in you test stack changes along the way!
+
+```ruby
+group :test do
+  gem 'minitest-spec-rails', '~> 3.1'
+end
+```
+
+#### Ruby 1.8 Users!!!
+
+If you are using Ruby 1.8, you must install a Test::Unit shim that subclasses MiniTest::Unit, just as Ruby 1.9 does. We have kindly packed up Ruby 1.9's `lib/test` directory in the [minitest-spec-rails-tu-shim](https://github.com/metaskills/minitest-spec-rails-tu-shim) gem. So just add this to your Gemfile.
+
+```ruby
+group :test do
+  gem 'minitest-spec-rails-tu-shim'
+end
+```
+
+
+### How is this different than MiniTest::Rails?
+
+To start off both Mike Moore (@blowmage) and I have worked together and we both LOVE MiniTest::Spec. Both projects aim to advocate MiniTest and make Rails integration as easy as possible. However, there are a few key differences in our projects. Some of these differences may go away in time too. As always, choose the tool you think fits your needs. So how, is minitest-spec-rails different than [minitest-rails](https://github.com/blowmage/minitest-rails)?
+
+  * We aim to leverage existing Rails test directories and files!
+  * No special test helper and/or generators.
+  * Easy migration path for existing Rails applications.
+  * How we go about freedom patching Rails.
+  * Fully support Ruby 1.8.7 with all legacy Test::Unit behavior.
+  * Compatibility with ActiveSupport::TestCase's setup and teardowns.
+
+So the goal of this project is to make Rails 3 or 4 applications just work as if rails-core had decided to support MiniTest::Spec all along. We believe that eventually that day will come and when it does, all your tests will still work! So bundle up and get started!
+
+```ruby
+gem 'minitest-spec-rails'
+```
+
+
+## Test Styles
+
+This <a href="http://cheat.errtheblog.com/s/minitest">cheat sheet</a> shows both the MiniTest::Unit assertions along with the MiniTest::Spec assertion syntax. Remember, MiniTest::Spec is built on top of MiniTest::Unit which is a Test::Unit replacement. That means you can mix and match styles as you upgrade from Test::Unit to a more modern style. For example, both of these would work in MiniTest::Spec and are interchangeable.
+
+```ruby
+# MiniTest::Unit Assertion Style:
+assert_equal 100, foo
+
+# MiniTest::Spec Assertion Style:
+foo.must_equal 100
+```
+
+
+```ruby
+require 'test_helper'
+class UserTest < ActiveSupport::TestCase
+  let(:user_ken)   { User.create! :email => 'ken@metaskills.net' }
+  it 'works' do
+    user_ken.must_be_instance_of User
+  end
+end
+```
+
+```ruby
+require 'test_helper'
+describe User do
+  # This will work too.
+end
+```
+
+Just for reference, here is a full list of each of Rails test case classes and the matching describe alternative if one exists. Remember, names are important when using the describe syntax. So, you can not have a mailer named `FooBar` and expect it to work with the outer describe spec style since there is no way to map the spec type based on an existing naming convention.
+
+```ruby
+# Model Test
+class UserTest < ActiveSupport::TestCase
+end
+describe User do
+end
+
+# Controller Test
+class UsersControllerTest < ActionController::TestCase
+end
+describe UsersController do
+end
+
+# Integration Tests - Must use subclass style!
+class IntegrationTest < ActionDispatch::IntegrationTest
+end
+
+# Mailer Test
+class UserMailerTest < ActionMailer::TestCase
+end
+describe UserMailer do
+end
+
+# View Helper Test
+class UsersHelperTest < ActionView::TestCase
+end
+describe UsersHelper do
+end
+```
+
+
+## Extras
+
+We have baked in a few extra methods behind the scenes to minitest-spec-rails. Most directly support our needs to reflect on described classes, however, they may be useful to you too when meta-programming on top of minitest-spec-rails.
+
+### #described_class
+The `described_class` method is available both via a class method and an instance method in any Rails test case. It is guaranteed to work despite the described level too. This allows class level macros to be built, much like Shoulda. Remember, it can only do this if you follow Rails naming conventions for your tests.
+
+```ruby
+class UserTest < ActiveSupport::TestCase
+  described_class # => User(id: integer, email: string)
+  it 'works here' do
+    described_class # => User(id: integer, email: string)
+  end
+  describe 'and' do
+    it 'works here too' do
+      described_class # => User(id: integer, email: string)
+    end
+  end
+end
+```
+
+### Setup & Teardown Compatability
+
+Rails ActiveSupport::TestCase allows multiple setup and teardown methods per class. It also allows you to specify these either with a symbol or a block. Unlike normal ActiveSupport setup and teardown callbacks, our blocks are evaluated in the scope of the instance, just like before and after. So this just works!
+
+```ruby
+class ActiveSupportCallbackTest < ActiveSupport::TestCase
+
+  setup :foo
+  setup :bar
+  before { @bat = 'biz' }
+
+  it 'works' do
+    @foo.must_equal 'foo'
+    @bar.must_equal 'bar'
+    @bat.must_equal 'biz'
+  end
+
+  private
+
+  def foo ; @foo = 'foo' ; end
+  def bar ; @bar = 'bar' ; end
+
+end
+```
+
+### mini_shoulda
+
+If you are migrating away from Shoulda, then minitest-spec-rails' mini_shoulda feature will help. To enable it, set the following configuration in your test environment file.
+
+```ruby
+# In config/environments/test.rb
+config.minitest_spec_rails.mini_shoulda = true
+```
+
+Doing so only enables a few aliases that allow the Shoulda `context`, `should`, and `should_eventually` methods. The following code demonstrates the full features of the mini_shoulda implementation. It basically replaces the shell of [should-context](https://github.com/thoughtbot/shoulda-context) in a few lines of code.
+
+```ruby
+class PostTests < ActiveSupport::TestCase
+  setup    { @post = Post.create! :title => 'Test Title', :body => 'Test body' }
+  teardown { Post.delete_all }
+  should 'work' do
+    @post.must_be_instance_of Post
+  end
+  context 'with a user' do
+    should_eventually 'have a user' do
+      # ...
+    end
+  end
+end
+```
+
+If you are in the assertions provided by shoulda-context like `assert_same_elements`, then you may want to consider copying them [from here](https://github.com/thoughtbot/shoulda-context/blob/master/lib/shoulda/context/assertions.rb) and including them in `MiniTest::Spec` yourself. I personally recommend just replacing these assertions with something more modern. A few examples are below.
+
+```ruby
+assert_same_elements a, b  # From
+a.sort.must_equal b.sort   # To
+
+assert_does_not_contain a, b  # From
+a.wont_include b              # To
+```
+
+### Matchers
+
+**I highly suggest that you stay away from matchers** since MiniTest::Spec gives you all the tools you need to write good tests. Staying away from matchers will make your code's tests live longer. So my advice is to stay away from things like `.should ==` and just write `.must_equal` instead. However, if matchers are really your thing, I recommend the [minitest-matchers](https://github.com/zenspider/minitest-matchers) gem. You can also check out the [valid_attribute](https://github.com/bcardarella/valid_attribute) gem built on top of minitest-matchers.
+
+```ruby
+describe Post do
+  subject { Post.new }
+  it { must have_valid(:title).when("Hello") }
+  it { wont have_valid(:title).when("", nil, "Bad") }
+end
+```
+
+
+## Gotchas
+
+### Assertion Methods
+
+If you are upgrading from Test::Unit, there are a few missing assertions that have been renamed or are no longer available within MiniTest.
+
+* The method `assert_raise` is renamed `assert_raises`.
+* There is no method `assert_nothing_raised`. There are good reasons for this on [Ryan's blog entry](http://blog.zenspider.com/blog/2012/01/assert_nothing_tested.html).
+
+### Mocha
+
+If you are using [Mocha](https://github.com/freerange/mocha) for mocking and stubbing, please update to the latest, 0.13.1 or higher so it is compatible with the latest MiniTest. If you do not like the deprecation warnings in older versions of Rails, just add this below the `require 'rails/all'` within your `application.rb` file :)
+
+```ruby
+require 'mocha/deprecation'
+Mocha::Deprecation.mode = :disabled
+```
+
+### Rails 3.0.x
+
+If you are using minitest-spec-rails with Rails 3.0, then your controller and mailer tests will need to use the `tests` interface for the assertions to be setup correctly within sub `describe` blocks. I think this is a bug with `class_attribute` within Rails 3.0 only. So use the following patterns.
+
+```ruby
+class UsersControllerTest < ActionController::TestCase
+  tests UsersController
+end
+class UserMailerTest < ActionMailer::TestCase
+  tests UserMailer
+end
+```
+
+### Rails 3.1 & 3.2
+
+If your view helper tests give you an eror like this: `RuntimeError: In order to use #url_for, you must include routing helpers explicitly.`, this is something that is broken only for Rails 3.1 and 3.2, both 3.0 and 4.0 and above do not exhibit this error. I have heard that if you `include Rails.application.routes.url_helpers` in your tests or inject them into the helper module before the test it may work. Lemme know what you find out.
+
+
+## Contributing
+
+We run our tests on [Travis CI](http://travis-ci.org/metaskills/minitest-spec-rails). If you detect a problem, open up a github issue or fork the repo and help out. After you fork or clone the repository, the following commands will get you up and running on the test suite.
+
+```shell
+$ bundle install
+$ bundle exec rake appraisal:setup
+$ bundle exec rake appraisal test
+```
+
+We use the [appraisal](https://github.com/thoughtbot/appraisal) gem from Thoughtbot to help us generate the individual gemfiles for each Rails version and to run the tests locally against each generated Gemfile. The `rake appraisal test` command actually runs our test suite against all Rails versions in our `Appraisal` file. If you want to run the tests for a specific Rails version, use `rake -T` for a list. For example, the following command will run the tests for Rails 4.1 only.
+
+```shell
+$ bundle exec rake appraisal:rails41 test
+```
+
+We have a few branches for each major Rails version.
+
+* [2-3-stable](https://github.com/metaskills/minitest-spec-rails/tree/2-3-stable) - Tracks Rails 2.3.x with MiniTest 4.x.
+* [3-x-stable](https://github.com/metaskills/minitest-spec-rails/tree/3-x-stable) - Oddly tracks Rails 3.x and 4.0 with MiniTest 4.x.
+* master - Currently tracks Rails 4.1 which uses Minitest 5.0.
+
+Our current build status is:
+[![Build Status](https://secure.travis-ci.org/metaskills/minitest-spec-rails.png)](http://travis-ci.org/metaskills/minitest-spec-rails)
+

data/Rakefile

@@ -0,0 +1,19 @@
+require 'rubygems'
+require 'bundler/gem_tasks'
+require 'rake/testtask'
+require 'appraisal'
+
+Rake::TestTask.new   do |t|
+  t.libs = ['lib','test']
+  t.test_files = Dir.glob("test/**/*_test.rb").sort
+  t.verbose = true
+end
+
+task :default => :test
+
+desc "Setup Appraisal."
+task 'appraisal:setup' do
+  Rake::Task['appraisal:cleanup'].invoke
+  Rake::Task['appraisal:gemfiles'].invoke
+  Rake::Task['appraisal:install'].invoke
+end

data/lib/minitest-spec-rails/dsl.rb

@@ -0,0 +1,41 @@
+module MiniTestSpecRails
+  module DSL
+
+    def self.included(klass)
+      klass.extend ClassMethods
+      remove_method :test if method_defined?(:test)
+    end
+
+    module ClassMethods
+
+      def describe(*args, &block)
+        stack = Minitest::Spec.describe_stack
+        stack.push self if stack.empty?
+        super(*args) { class_eval(&block) }
+        stack.pop if stack.length == 1
+      end
+
+      def before(type = nil, &block)
+        setup { self.instance_eval(&block) }
+      end
+
+      def after(type = nil, &block)
+        teardown { self.instance_eval(&block) }
+      end
+
+      def test(name, &block)
+        it(name) { self.instance_eval(&block) }
+      end
+
+      def described_class
+        nil
+      end
+      
+    end
+
+    def described_class
+      self.class.described_class
+    end
+    
+  end
+end

data/lib/minitest-spec-rails/init/action_controller.rb

@@ -0,0 +1,26 @@
+module MiniTestSpecRails
+  module Init
+    module ActionControllerBehavior
+
+      extend ActiveSupport::Concern
+
+      included do
+        extend Descriptions
+        register_spec_type(self) { |desc| Class === desc && desc < ActionController::Metal }
+        register_spec_type(/Controller( ?Test)?\z/, self)
+        register_spec_type(self) { |desc| Class === desc && desc < self }
+      end
+      
+      module Descriptions
+
+        def described_class
+          determine_default_controller_class(name)
+        end
+
+      end
+
+    end
+  end
+end
+
+ActionController::TestCase.send :include, MiniTestSpecRails::Init::ActionControllerBehavior

data/lib/minitest-spec-rails/init/action_dispatch.rb

@@ -0,0 +1,16 @@
+module MiniTestSpecRails
+  module Init
+    module ActionDispatchBehavior
+
+      extend ActiveSupport::Concern
+
+      included do
+        register_spec_type(/(Acceptance|Integration) ?Test\z/, self)
+        register_spec_type(self) { |desc| Class === desc && desc < self }
+      end
+
+    end
+  end
+end
+
+ActionDispatch::IntegrationTest.send :include, MiniTestSpecRails::Init::ActionDispatchBehavior

data/lib/minitest-spec-rails/init/action_mailer.rb

@@ -0,0 +1,27 @@
+module MiniTestSpecRails
+  module Init
+    module ActionMailerBehavior
+
+      extend ActiveSupport::Concern
+
+      included do
+        register_spec_type(self) { |desc| Class === desc && desc < ActionMailer::Base }
+        register_spec_type(/Mailer( ?Test)?\z/, self)
+        register_spec_type(self) { |desc| Class === desc && desc < self }
+        extend Descriptions
+      end
+
+      module Descriptions
+
+        def described_class
+          determine_default_mailer(name)
+        end
+
+      end
+
+    end
+  end
+end
+
+ActionMailer::TestCase.send :include, MiniTestSpecRails::Init::ActionMailerBehavior
+

data/lib/minitest-spec-rails/init/action_view.rb

@@ -0,0 +1,26 @@
+module MiniTestSpecRails
+  module Init
+    module ActionViewBehavior
+
+      extend ActiveSupport::Concern
+
+      included do
+        class_attribute :_helper_class
+        register_spec_type(/(Helper|View)( ?Test)?\z/, self)
+        register_spec_type(self) { |desc| Class === desc && desc < self }
+        extend Descriptions
+      end
+
+      module Descriptions
+
+        def described_class
+          determine_default_helper_class(name)
+        end
+
+      end
+
+    end
+  end
+end
+
+ActionView::TestCase.send :include, MiniTestSpecRails::Init::ActionViewBehavior

data/lib/minitest-spec-rails/init/active_support.rb

@@ -0,0 +1,35 @@
+module MiniTestSpecRails
+  module Init
+    module ActiveSupportBehavior
+
+      extend ActiveSupport::Concern
+
+      included do
+        singleton_class.class_eval { remove_method :describe }
+        extend MiniTest::Spec::DSL
+        include MiniTestSpecRails::DSL
+        include ActiveSupport::Testing::ConstantLookup
+        extend Descriptions
+        register_spec_type(self) { |desc| Class === desc }
+      end
+
+      module Descriptions
+
+        def described_class
+          determine_constant_from_test_name(name) do |constant|
+            Class === constant
+          end
+        end
+
+      end
+
+      def initialize(*args)
+        Thread.current[:current_spec] = self
+        super
+      end
+
+    end
+  end
+end
+
+ActiveSupport::TestCase.send :include, MiniTestSpecRails::Init::ActiveSupportBehavior