thincloud-test-rails 1.0.0.pre

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/.ruby-version

@@ -0,0 +1 @@
+1.9.3@thincloud-test-rails

data/Gemfile

@@ -0,0 +1,3 @@
+source "https://rubygems.org"
+
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Phil Cohen
+
+MIT License
+
+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,87 @@
+# thincloud-test-rails [![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/newleaders/thincloud-test-rails)
+
+## Description
+
+Opinionated testing framework dependencies and configuration for Rails applications, built on [`thincloud-test`](http://newleaders.github.com/thincloud-test).
+
+[New Leaders](https://newleaders.com) uses this gem to manage the following dependencies:
+
+* [capybara](https://github.com/jnicklas/capybara)
+* [database_cleaner](https://github.com/bmabey/database_cleaner)
+* [factory_girl_rails](https://github.com/thoughtbot/factory_girl_rails)
+* [minitest-rails](https://github.com/blowmage/minitest-rails)
+* [minitest-rails-capybara](https://github.com/blowmage/minitest-rails-capybara)
+* [minitest-rails-shoulda](https://github.com/bousquet/minitest-rails-shoulda)
+* [shoulda-matchers](https://github.com/thoughtbot/shoulda-matchers)
+
+
+## Requirements
+
+### Ruby
+
+This gem has been tested against the following Ruby versions:
+
+* 1.9.3
+
+### Rails
+
+This gem requires Rails 3.2.11+ and has been tested on the following versions:
+
+* 3.2
+
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+``` ruby
+gem "thincloud-test-rails"
+```
+
+And then execute:
+
+```
+$ bundle
+```
+
+Or install it yourself as:
+
+```
+$ gem install thincloud-test-rails
+```
+
+
+## Usage
+
+The gem manages the test framework dependencies for you and provides a generator (`thincloud:test`) to bootstrap a test environment for your Rails application.
+
+To configure your application in one easy step, run the following:
+
+```
+$ rails g thincloud:test
+```
+
+This generator will do the following:
+
+* Remove any existing `Test::Unit`-generated content
+* Run the `mini_test:install` generator for `minitest-rails`
+* Add `test/support/*` files which match New Leaders conventions
+* Inject a line into `config/application.rb` to require the `thincloud/test/rails/railtie` file
+
+Once this is complete, you will have a complete test setup. Run `rake` and enjoy! :tada: :balloon:
+
+
+## Contributing
+
+1. [Fork it](https://github.com/newleaders/thincloud-test-rails/fork_select)
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. [Create a Pull Request](https://github.com/newleaders/thincloud-test-rails/pull/new)
+
+
+## License
+
+* Freely distributable and licensed under the [MIT license](http://newleaders.mit-license.org/2013/license.html).
+* Copyright (c) 2013 New Leaders ([opensource@newleaders.com](opensource@newleaders.com))
+* [https://newleaders.com](https://newleaders.com)

data/Rakefile

@@ -0,0 +1,26 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'Thincloud::Test'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../test/dummy/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+Bundler::GemHelper.install_tasks

data/lib/generators/thincloud/templates/minitest_helper.rb

@@ -0,0 +1,21 @@
+if RUBY_ENGINE == "ruby"
+  begin
+    require "simplecov"
+    SimpleCov.start "rails" do
+      add_filter "test"
+      add_filter "config"
+      command_name "MiniTest"
+    end
+  rescue LoadError
+    warn "unable to load SimpleCov"
+  end
+end
+
+ENV["RAILS_ENV"] = "test"
+require File.expand_path("../../config/environment", __FILE__)
+
+require "thincloud-test-rails"
+
+# Requires supporting ruby files with custom matchers and macros, etc,
+# in spec/support/ and its subdirectories.
+Dir[File.join("./test/support/**/*.rb")].sort.each { |f| require f }

data/lib/generators/thincloud/templates/support/capybara.rb

@@ -0,0 +1,10 @@
+require "minitest/rails/capybara"
+
+class MiniTest::Rails::ActionDispatch::IntegrationTest
+
+  # Public: Reset the Capybara session after every run.
+  teardown do
+    Capybara.reset_sessions!
+  end
+
+end

data/lib/generators/thincloud/templates/support/database_cleaner.rb

@@ -0,0 +1,12 @@
+DatabaseCleaner.strategy = :transaction
+DatabaseCleaner.clean_with :truncation
+
+class MiniTest::Spec
+  before :each do
+    DatabaseCleaner.start
+  end
+
+  after :each do
+    DatabaseCleaner.clean
+  end
+end

data/lib/generators/thincloud/templates/support/factory_girl.rb

@@ -0,0 +1,4 @@
+class MiniTest::Spec
+  include FactoryGirl::Syntax::Methods
+end
+FactoryGirl.find_definitions

data/lib/generators/thincloud/templates/support/minitest_rails.rb

@@ -0,0 +1,8 @@
+class MiniTest::Rails::ActiveSupport::TestCase
+  # Register any classes that respond to validate to a specific test class
+  Minitest::Spec.register_spec_type(self) do |desc|
+    desc.respond_to?(:validate)
+  end
+end
+
+MiniTest::Rails.override_testunit!

data/lib/generators/thincloud/templates/support/routing_spec.rb

@@ -0,0 +1,12 @@
+class RoutingSpec < MiniTest::Rails::ActiveSupport::TestCase
+  include ::ActionDispatch::Assertions::RoutingAssertions
+  include ::Rails.application.routes.url_helpers
+
+  # Test subjects containing 'Routes' are treated as Routing tests
+  #   e.g. describe "Product Routes" do ...
+  register_spec_type /Routes/, self
+
+  before do
+    @routes = ::Rails.application.routes
+  end
+end

data/lib/generators/thincloud/test_generator.rb

@@ -0,0 +1,54 @@
+require "rails"
+require "thincloud/test/test_generator"
+
+module Thincloud
+  class TestGenerator < ::Rails::Generators::Base
+    source_root File.expand_path("../templates", __FILE__)
+
+    def thincloud_test_init
+      ::Thincloud::Test::TestGenerator.new.testify!(minitest: false)
+    end
+
+    desc "Generates thincloud test infrastructure."
+    def test
+      remove_test_unit
+
+      setup_minitest_rails
+
+      directory "support", "test/support"
+
+      inject_into_file "config/application.rb", before: "if defined?(Bundler)" do
+        <<-EOS
+# initialize thincloud-test-rails
+require "thincloud/test/rails/railtie"\n\n
+        EOS
+      end
+
+      say_status "", ""
+      say_status "success", "thincloud-test-rails has finished."
+    end
+
+
+    private
+
+    def setup_minitest_rails
+      generate "mini_test:install"
+      remove_file "test/minitest_helper.rb"
+
+      copy_file "minitest_helper.rb", "test/minitest_helper.rb"
+
+      empty_directory "test/factories"
+      create_file "test/factories/.gitkeep"
+    end
+
+    def remove_test_unit
+      remove_file "test/test_helper.rb"
+
+      remove_dir "test/functional"
+      remove_dir "test/integration"
+      remove_dir "test/performance"
+      remove_dir "test/unit"
+    end
+
+  end
+end

data/lib/thincloud-test-rails.rb

@@ -0,0 +1,17 @@
+require "thincloud/test/rails"
+
+require "database_cleaner"  # reset database on each test run
+
+require "thincloud/test"
+
+require "minitest/rails"
+require "minitest-rails-shoulda"
+
+require "factory_girl"
+
+module Thincloud
+  module Test
+    module Rails
+    end
+  end
+end

data/lib/thincloud/test/rails.rb

@@ -0,0 +1,2 @@
+require "thincloud/test/rails/version"
+require "thincloud/test/rails/railtie"

data/lib/thincloud/test/rails/railtie.rb

@@ -0,0 +1,17 @@
+require "rails"
+
+module Thincloud
+  module Test
+    module Rails
+      class Railtie < ::Rails::Railtie
+
+        initializer "thincloud.test.rails.generators" do |app|
+          app.config.generators do |g|
+            g.test_framework :mini_test, spec: true, fixture: false
+          end
+        end
+
+      end
+    end
+  end
+end

data/lib/thincloud/test/rails/version.rb

@@ -0,0 +1,7 @@
+module Thincloud
+  module Test
+    module Rails
+      VERSION = "1.0.0.pre"
+    end
+  end
+end

data/test/dummy/.gitignore

@@ -0,0 +1 @@
+coverage

data/test/dummy/Guardfile

@@ -0,0 +1,17 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+guard "minitest" do
+  # with Minitest::Spec
+  watch(%r|^test/(.*)_test\.rb|)
+  watch(%r|^lib/(.*)([^/]+)\.rb|)      { |m| "test/#{m[1]}#{m[2]}_test.rb" }
+  watch(%r|^test/minitest_helper\.rb|) { "test" }
+  watch(%r|^test/support/|)            { "test" }
+
+  # Rails 3.2
+  watch(%r|^app/controllers/(.*)\.rb|) { |m| "test/controllers/#{m[1]}_test.rb" }
+  watch(%r|^app/mailers/(.*)\.rb|)     { |m| "test/mailers/#{m[1]}_test.rb" }
+  watch(%r|^app/helpers/(.*)\.rb|)     { |m| "test/helpers/#{m[1]}_test.rb" }
+  watch(%r|^app/models/(.*)\.rb|)      { |m| "test/models/#{m[1]}_test.rb" }
+end
+

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.