omghax-test_rails 1.0.0 → 1.1.0

data/History.txt

@@ -1,3 +1,9 @@
+=== 1.1.0 / 2009-05-21
+
+* 1 minor enhancement:
+
+  * Test::Rails is now compatible with Rails 2.3.2, thanks to Erik Ostrom.
+
 === 1.0.0 / 2009-03-12
 
 * 1 major enhancement:

data/Manifest.txt

@@ -19,3 +19,4 @@ test/test_rails_controller_test_case.rb
 test/test_rails_helper_test_case.rb
 test/test_rails_view_test_case.rb
 test/test_zentest_assertions.rb
+test_rails.gemspec

data/README.txt

@@ -1,68 +1,84 @@
-= ZenTest
+= Test::Rails
 
 * http://www.zenspider.com/ZSS/Products/ZenTest/
 * http://rubyforge.org/projects/zentest/
 * mailto:ryand-ruby@zenspider.com
 
+Test::Rails was dropped from ZenTest for the 4.0 release, but there
+are still a lot of tests that use it.  This is Dray Lacy's extraction of
+Test::Rails from ZenTest, updated to work with Rails 2.3.2 (at least
+partially).
+
 == DESCRIPTION
 
-ZenTest provides 4 different tools and 1 library: zentest, unit_diff,
-autotest, multiruby, and Test::Rails.
+Test::Rails helps you build industrial-strength Rails code.
+
+== FEATURES
 
-ZenTest scans your target and unit-test code and writes your missing
-code based on simple naming rules, enabling XP at a much quicker
-pace. ZenTest only works with Ruby and Test::Unit.
+* Test your controllers and views in isolation from each other.
+* Test helper methods in isolation from your controllers, including those that
+  use routing.
+* Test::Rails provides some helpful assertions for dealing with collections,
+  like #assert_empty and #assert_includes, as well as negated versions
+  (#deny_empty, #deny_includes, etc.)
 
-unit_diff is a command-line filter to diff expected results from
-actual results and allow you to quickly see exactly what is wrong.
+== SYNOPSYS
 
-autotest is a continous testing facility meant to be used during
-development. As soon as you save a file, autotest will run the
-corresponding dependent tests.
+  # Typical View Test
+  class RouteViewTest < Test::Rails::ViewTestCase
 
-multiruby runs anything you want on multiple versions of ruby. Great
-for compatibility checking! Use multiruby_setup to manage your
-installed versions.
+    fixtures :users, :routes, :points, :photos
 
-Test::Rails helps you build industrial-strength Rails code.
+    def test_delete
+      # Set up instance variables for template
+      assigns[:loggedin_user] = users(:herbert)
+      assigns[:route] = routes(:work)
 
-== STRATEGERY
+      # render template for the delete action in RouteController
+      render
 
-There are two strategeries intended for ZenTest: test conformance
-auditing and rapid XP.
+      # assert that there's a form with an action of "/route/destroy"
+      assert_form form_url, :post do
+        # with a hidden id field
+        assert_input :hidden, :id
+        # And a submit button that says 'Delete!'
+        assert_submit 'Delete!'
+      end
 
-For auditing, ZenTest provides an excellent means of finding methods
-that have slipped through the testing process. I've run it against my
-own software and found I missed a lot in a well tested
-package. Writing those tests found 4 bugs I had no idea existed.
+      # And a link back to the route so you don't delete it
+      assert_links_to "/route/show/#{routes(:work).id}", 'No, I do not!'
+    end
 
-ZenTest can also be used to evaluate generated code and execute your
-tests, allowing for very rapid development of both tests and
-implementation.
+  end
 
-== FEATURES
+  # Typical Layout Test
+  require 'test/test_helper'
 
-* Scans your ruby code and tests and generates missing methods for you.
-* Includes a very helpful filter for Test::Unit output called unit_diff.
-* Continually and intelligently test only those files you change with autotest.
-* Test against multiple versions with multiruby.
-* Enhance and automatically audit your rails tests using Test::Rails.
-* Includes a LinuxJournal article on testing with ZenTest written by Pat Eyler.
-* See also: http://blog.zenspider.com/archives/zentest/
-* See also: http://blog.segment7.net/articles/category/zentest
+  # Create a dummy controller for layout views. This lets the setup use the
+  # right path with minimum fuss.
+  class LayoutsController < ApplicationController; end
 
-== SYNOPSYS
+  class LayoutsViewTest < Test::Rails::ViewTestCase
 
-  ZenTest MyProject.rb TestMyProject.rb > missing.rb
+    fixtures :users, :routes, :points, :photos
 
-  ./TestMyProject.rb | unit_diff
+    def test_default
+      # Template set-up
+      @request.request_uri = '/foo'
+      assigns[:action_title] = 'Hello & Goodbye'
 
-  autotest
+      # Render an empty string with the 'application' layout.
+      render :text => '', :layout => 'application'
 
-  multiruby_setup mri:svn:current
-  multiruby ./TestMyProject.rb
+      # Assert content just like a regular view test.
+      assert_links_to '/', 'Home'
+      assert_links_to '/user', 'Login'
+      deny_links_to '/user/logout', 'Logout'
+      assert_title 'Hello &amp; Goodbye'
+      assert_h 1, 'Hello &amp; Goodbye'
+    end
 
-  (and other stuff for Test::Rails)
+  end
 
 == REQUIREMENTS
 
@@ -70,18 +86,18 @@ implementation.
 * Test::Unit or miniunit
 * Hoe
 * rubygems
-* diff.exe on windoze. Try http://gnuwin32.sourceforge.net/packages.html
+* Rails 2.3.2 (for older versions of Rails, use Test::Rails 1.0.0)
 
 == INSTALL
 
 Using Rubygems:
 
-* sudo gem install ZenTest
+* sudo gem install omghax-test_rails -s http://gems.github.com
 
 Using Rake:
 
 * rake test
-* sudo rake install
+* sudo rake install_gem
 
 == LICENSE
 

data/lib/test/rails.rb

@@ -277,6 +277,10 @@ class Object # :nodoc:
   end
 end
 
+require 'active_support'
+require 'active_support/test_case'
+require 'active_record/fixtures'
+
 require 'test/zentest_assertions'
 require 'test/rails/test_case'
 require 'test/rails/functional_test_case'
@@ -288,7 +292,7 @@ require 'test/rails/view_test_case'
 ##
 # Use sensible defaults.
 
-class Test::Unit::TestCase # :nodoc:
+class ActiveSupport::TestCase # :nodoc:
   self.use_transactional_fixtures = true
   self.use_instantiated_fixtures  = false
 end

data/lib/test/rails/controller_test_case.rb

@@ -112,9 +112,6 @@
 
 class Test::Rails::ControllerTestCase < Test::Rails::FunctionalTestCase
 
-  self.use_transactional_fixtures = true
-  self.use_instantiated_fixtures = false
-
   NOTHING = Object.new # :nodoc:
 
   DEFAULT_ASSIGNS = %w[

data/lib/test/rails/functional_test_case.rb

@@ -6,8 +6,8 @@ $TESTING_RTC = defined?($TESTING_RTC) && $TESTING_RTC
 
 class Test::Rails::FunctionalTestCase < Test::Rails::TestCase
 
-  self.use_transactional_fixtures = true
-  self.use_instantiated_fixtures = false
+  include ActionController::Assertions::SelectorAssertions
+  include ActionController::TestProcess
 
   ##
   # Sets up instance variables to allow tests depending on a controller work.

data/lib/test/rails/helper_test_case.rb

@@ -23,9 +23,6 @@ end
 
 class Test::Rails::HelperTestCase < Test::Rails::FunctionalTestCase
 
-  self.use_transactional_fixtures = true
-  self.use_instantiated_fixtures = false
-
   # Are other helpers needed?
 
   include ActionView::Helpers::ActiveRecordHelper

data/lib/test/rails/test_case.rb

@@ -3,14 +3,10 @@
 #--
 # Eventually this will hold the fixture setup stuff.
 
-class Test::Rails::TestCase < Test::Unit::TestCase
+class Test::Rails::TestCase < ActiveSupport::TestCase
 
   undef_method :default_test
 
-  # Set defaults because Rails has poor ones (and these don't inherit properly)
-  self.use_transactional_fixtures = true
-  self.use_instantiated_fixtures = false
-
 end
 
 module Test::Unit::Assertions

data/lib/test/rails/version.rb

@@ -2,7 +2,7 @@ module Test
   module Rails
     module VERSION # :nodoc:
       MAJOR = 1
-      MINOR = 0
+      MINOR = 1
       TINY = 0
 
       STRING = [MAJOR, MINOR, TINY].join('.')

data/lib/test/rails/view_test_case.rb

@@ -95,9 +95,6 @@
 
 class Test::Rails::ViewTestCase < Test::Rails::FunctionalTestCase
 
-  self.use_transactional_fixtures = true
-  self.use_instantiated_fixtures = false
-
   ##
   # Sets up the test case.
 
@@ -204,7 +201,7 @@ class Test::Rails::ViewTestCase < Test::Rails::FunctionalTestCase
   #
   # If a view cannot be found the test will flunk.
 
-  def render(options = {}, deprecated_status = nil)
+  def render(options = {}, *rest_args)
     @action_name = action_name caller[0] if options.empty?
     assigns[:action_name] = @action_name
 
@@ -238,7 +235,7 @@ class Test::Rails::ViewTestCase < Test::Rails::FunctionalTestCase
 
     # Do the render
     options[:TR_force] = true
-    @controller.render options, deprecated_status
+    @controller.send(:render, options, *rest_args)
 
     # Rails 1.1
     @controller.send :process_cleanup rescue nil

data/test/test_help.rb

@@ -22,7 +22,10 @@ module ActionView::Helpers::FormHelper; end
 module ActionView::Helpers::UrlHelper; end
 module ActionView::Helpers::AssetTagHelper; end
 
-class << Test::Unit::TestCase
+# ActiveSupport
+require 'active_support'
+require 'active_support/test_case'
+class << ActiveSupport::TestCase
   attr_accessor :use_transactional_fixtures
   attr_accessor :use_instantiated_fixtures
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: omghax-test_rails
 version: !ruby/object:Gem::Version 
-  version: 1.0.0
+  version: 1.1.0
 platform: ruby
 authors: 
 - Ryan Davis
@@ -11,7 +11,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-03-12 00:00:00 -07:00
+date: 2009-05-21 00:00:00 -07:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -24,7 +24,7 @@ dependencies:
       - !ruby/object:Gem::Version 
         version: 1.8.3
     version: 
-description: "ZenTest provides 4 different tools and 1 library: zentest, unit_diff, autotest, multiruby, and Test::Rails.  ZenTest scans your target and unit-test code and writes your missing code based on simple naming rules, enabling XP at a much quicker pace. ZenTest only works with Ruby and Test::Unit.  unit_diff is a command-line filter to diff expected results from actual results and allow you to quickly see exactly what is wrong.  autotest is a continous testing facility meant to be used during development. As soon as you save a file, autotest will run the corresponding dependent tests.  multiruby runs anything you want on multiple versions of ruby. Great for compatibility checking! Use multiruby_setup to manage your installed versions.  Test::Rails helps you build industrial-strength Rails code."
+description: Test::Rails helps you build industrial-strength Rails code.
 email: 
 - ryand-ruby@zenspider.com
 - drbrain@segment7.net
@@ -85,7 +85,7 @@ rubyforge_project: test_rails
 rubygems_version: 1.2.0
 signing_key: 
 specification_version: 2
-summary: "ZenTest provides 4 different tools and 1 library: zentest, unit_diff, autotest, multiruby, and Test::Rails"
+summary: Test::Rails helps you build industrial-strength Rails code.
 test_files: 
 - test/test_help.rb
 - test/test_rails_controller_test_case.rb