quicktest 0.3.4 → 0.4.0

data/README

@@ -86,12 +86,20 @@ http://gregweber.info/projects/quicktest.html
 http://quicktest.rubyforge.org/
 
 == Important Notes
-- def quicktest will instantiate an object for the class you are testing, which gives a convenient referenct to self in the quicktest method.  However, it calls new() without any parameters.  If you need parameters for new(), you will have to use def self.quicktest.
+- to test a module instance method, you must define an object that the module will be included into by defining the following in the module:
+
+  def self.quicktest_include_into; Object end
+
+- def quicktest will instantiate an object for the class you are testing, which gives a convenient referenct to self in the quicktest method.  However, it calls new() without any parameters.  If you need parameters for new(), you will have to use def self.quicktest and call new() yourself
 - quicktest methods not working properly? if the class (or one of its ancestors) is overriding method tracing then including QuickTest::Tracer will fix it.
 
 == Unimportant Notes
 === production performance
-leaving test code in with your production code is not necessarily a good idea, but there is almost no runtime overhead to doing so since ruby will not evaluate code in a method until the method is invoked
+leaving test code in with your production code is not necessarily a good idea, but there is almost no runtime overhead to doing so since ruby will not evaluate code in a method until the method is invoked.  You can also put
+
+  remove_method :quicktest
+
+at the bottom of a class to completely remove the quicktest method
 
 === rationals
 * tests for scripts
@@ -101,7 +109,7 @@ You can have a flow of development where a 'quick and dirty' script becomes well
 * documentation
 Tests are a form of documentation.  It can be argued that it is better to have all documentation include in the source
 
-* efficient TDD
+* efficient TDD and prototyping
 When writing fresh code you now have the possibility to be directly next to the code under test without having to switch back and forth between files.  When you are done writing the new code, you can easily pull all the quicktest methods out and into a spec file.
 
 

data/doc/created.rid

@@ -1 +1 @@
-Thu, 06 Mar 2008 23:06:11 -0600
+Sat, 08 Mar 2008 00:15:37 -0600

data/lib/quicktest.rb

@@ -13,6 +13,11 @@ module QuickTest
 
     # set which code will be running the tests
     attr_accessor :runner, :runner_module
+
+    # when testing module instance methods
+    # this defines the class to include a module into
+    # user sets this by defining self.quicktest_include_into in a module
+    attr_accessor :include_module_into
   end
 
   # to reuse this implementation
@@ -123,6 +128,10 @@ module QuickTest
 
           if traced == :quicktest
             QuickTest.runner.new self
+
+          elsif traced == :quicktest_include_into
+            QuickTest.include_module_into = self.quicktest_include_into
+
           else
             QuickTest.runner.add_singleton_method traced
             __quicktest_singleton_method_added__ traced
@@ -138,10 +147,15 @@ module QuickTest
           return if traced == qt.runner.methods.last
 
           if traced == :quicktest
-            if self.class == Module
-              fail "to test module instance methods, include them in a class"
-            end
-            qt.runner.new self.new
+            qt.runner.new(
+              if self.class != Module
+                self.new
+              else
+                o = (QuickTest.include_module_into || (fail "to test module instance methods, include them in a class or define a method for the module 'self.quicktest_include_into'")).new
+                o.extend(self)
+                o
+              end
+            )
 
           else
             unless qt.ignore_first_method_added or

data/rakefile

@@ -80,13 +80,22 @@ namespace :readme do
   end
 end
 
+desc "release a new gem to rubyforge"
+task :release => [:rdoc,:package] do
+  Dir.chdir('pkg') do
+    release = Dir['*.gem'].sort_by {|file| File.mtime(file)}.last
+    release =~ /^[^-]+-([.0-9]+).gem$/
+    `rubyforge login && rubyforge add_release quicktest quicktest #$1 #{release}`
+  end
+end
+
 require 'rubygems'
 require 'rake/gempackagetask'
 
 spec = Gem::Specification.new do |s|
   s.name = "quicktest"
   s.rubyforge_project = "quicktest"
-  s.version = "0.3.4"
+  s.version = "0.4.0"
   s.author = "Greg Weber"
   s.email = "greg@gregweber.info"
   s.homepage = "http://quicktest.rubyfore.org/"

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.4
 specification_version: 1
 name: quicktest
 version: !ruby/object:Gem::Version 
-  version: 0.3.4
-date: 2008-03-07 00:00:00 -06:00
+  version: 0.4.0
+date: 2008-03-08 00:00:00 -06:00
 summary: utility for inlining tests with the code tested
 require_paths: 
 - lib
@@ -47,6 +47,7 @@ files:
 - doc/classes
 - lib/quicktest.rb
 - pkg/quicktest-0.3.2.gem
+- pkg/quicktest-0.3.4.gem
 - test/test.rb
 - test/test_result.txt
 - README