test_extensions 0.0.1 → 0.1.0

data/Readme

@@ -21,19 +21,21 @@ This is a collection of methods and features for Test::Unit that are missing fro
 
 === Useful assertion methods
 
-* assert_exception
-* assert_changed
-* assert_includes / assert_contains
+* <b><tt>assert_exception</tt></b>: make assetions about an exception that should be raised -- not just the _class_ of the exception but other details like the message
+* <b><tt>assert_includes</tt></b> / <tt>assert_contains</tt>:</b> assert that +haystack+ contains +needle+; works for anything that responds to <tt>include?</tt> (arrays, strings, ...)
+* <b><tt>assert_match Regexp.loose_join('key phrase 1', 'key phrase 2')</tt></b>
+  	assert_match Regexp.loose_join('key phrase 1', 'key phrase 2'), "Some really long string that you want to make sure contains both key phrase 1 and key phrase 2, in that order, but you don't care too much about the stuff in between, and you don't really want to hand-craft the regular expression or worry about escaping things like '.'s and '*'s yourself."
+* <b><tt>assert_changed</tt></b>: assert that a variable changed state during the course of the block (not really useful)
 
-See the documentation for each method for details. (These methods are currently part of http://qualitysmithext.rubyforge.org/)
+See the individual method documentation for each method for details. These methods are currently part of http://qualitysmithext.rubyforge.org/.
 
 Rails-specific:
 * assert_user_error
 
 === For testing command-line programs
 
-* <tt>capture_output</tt> -- captures the standard output/error from the method under test (rather than letting it print to the screen) so that you can make assertions about it.
-* <tt>simulate_input</tt> -- if your application is expecting some kind of user input on stdin, this method can be used to simulate the input, so that your test is completely automated and self-contained.
+* <b><tt>capture_output</tt></b> -- captures the standard output/error from the method under test (rather than letting it print to the screen) so that you can make assertions about it.
+* <b><tt>simulate_input</tt></b> -- if your application is expecting some kind of user input on stdin, this method can be used to simulate the input, so that your test is completely automated and self-contained.
 
 == Requirements
 

data/lib/test_extensions.rb

@@ -6,6 +6,7 @@ require 'facets/core/kernel/require_local'
 require_local 'test_extensions/test_colorizer'
 
 gem 'qualitysmith_extensions'
+require 'qualitysmith_extensions/regexp/join'
 require 'qualitysmith_extensions/kernel/capture_output.rb'
 require 'qualitysmith_extensions/kernel/simulate_input.rb'
 

metadata

@@ -3,15 +3,15 @@ rubygems_version: 0.9.2
 specification_version: 1
 name: test_extensions
 version: !ruby/object:Gem::Version 
-  version: 0.0.1
-date: 2007-04-30 00:00:00 -07:00
-summary: ...
+  version: 0.1.0
+date: 2007-05-01 00:00:00 -07:00
+summary: A collection of user-contributed enhancements and new methods for Test::Unit
 require_paths: 
 - lib
 email: 
-homepage: http://test_extensions.rubyforge.org
-rubyforge_project: test_extensions
-description: ...
+homepage: http://test-extensions.rubyforge.org
+rubyforge_project: test-extensions
+description: A collection of user-contributed enhancements and new methods for Test::Unit
 autorequire: 
 default_executable: 
 bindir: bin
@@ -58,6 +58,15 @@ dependencies:
       - !ruby/object:Gem::Version 
         version: 0.0.0
     version: 
+- !ruby/object:Gem::Dependency 
+  name: colored
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Version::Requirement 
+    requirements: 
+    - - ">"
+      - !ruby/object:Gem::Version 
+        version: 0.0.0
+    version: 
 - !ruby/object:Gem::Dependency 
   name: qualitysmith_extensions
   version_requirement: