minitest 2.10.0 → 2.10.1

data/.autotest

@@ -1,12 +1,13 @@
 # -*- ruby -*-
 
 require 'autotest/restart'
-require 'autotest/rcov'
+require 'autotest/rcov' if ENV['RCOV']
 
 Autotest.add_hook :initialize do |at|
   at.testlib = 'minitest/unit'
 
   at.extra_class_map["MiniTest::Spec"]           = "test/test_minitest_spec.rb"
+  at.extra_class_map["TestMeta"]                 = "test/test_minitest_spec.rb"
   at.extra_class_map["TestMiniTestUnitTestCase"] = "test/test_minitest_unit.rb"
   at.extra_class_map["TestMiniTestUnit"]         = "test/test_minitest_unit.rb"
   at.add_exception 'coverage.info'

data/History.txt

@@ -1,3 +1,9 @@
+=== 2.10.1 / 2012-01-17
+
+* 1 bug fix:
+
+  * Fixed stupid 1.9 path handling grumble grumble. (graaff)
+
 === 2.10.0 / 2011-12-20
 
 * 3 minor enhancements:

data/README.txt

@@ -44,7 +44,7 @@ implementors that need a minimal set of methods to bootstrap a working
 test suite. For example, there is no magic involved for test-case
 discovery.
 
-    "Again, I can’t praise enough the idea of a testing/specing
+    "Again, I can't praise enough the idea of a testing/specing
      framework that I can actually read in full in one sitting!"
 
     -- Piotr Szotkowski

data/lib/minitest/unit.rb

@@ -643,7 +643,7 @@ module MiniTest
   end
 
   class Unit # :nodoc:
-    VERSION = "2.10.0" # :nodoc:
+    VERSION = "2.10.1" # :nodoc:
 
     attr_accessor :report, :failures, :errors, :skips # :nodoc:
     attr_accessor :test_count, :assertion_count       # :nodoc:

data/test/metametameta.rb

@@ -19,9 +19,8 @@ class MetaMetaMetaTestCase < MiniTest::Unit::TestCase
     output = @output.string.dup
     output.sub!(/Finished tests in .*/, "Finished tests in 0.00")
     output.sub!(/Loaded suite .*/, 'Loaded suite blah')
-    output.gsub!(/[\w\/]+\/test\/[^:]+:\d+/, 'FILE:LINE')
-    output.gsub!(/(?:.\/)?test\/[^:]+:\d+/, 'FILE:LINE')
-    output.gsub!(/\[[^\]]+\]/, '[FILE:LINE]')
+    output.gsub!(/\[[^\]:]+:\d+\]/, '[FILE:LINE]')
+    output.gsub!(/^(\s+)[^:]+:\d+:in/, '\1FILE:LINE:in')
     assert_equal(expected, output)
   end
 

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: minitest
 version: !ruby/object:Gem::Version 
-  hash: 39
+  hash: 37
   prerelease: 
   segments: 
   - 2
   - 10
-  - 0
-  version: 2.10.0
+  - 1
+  version: 2.10.1
 platform: ruby
 authors: 
 - Ryan Davis
@@ -36,7 +36,7 @@ cert_chain:
   FBHgymkyj/AOSqKRIpXPhjC6
   -----END CERTIFICATE-----
 
-date: 2011-12-21 00:00:00 Z
+date: 2012-01-18 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: rdoc
@@ -68,26 +68,49 @@ dependencies:
         version: "2.12"
   type: :development
   version_requirements: *id002
-description: "minitest provides a complete suite of testing facilities supporting\n\
-  TDD, BDD, mocking, and benchmarking.\n\n    \"I had a class with Jim Weirich on testing last week and we were\n     allowed to choose our testing frameworks. Kirk Haines and I were\n     paired up and we cracked open the code for a few test\n     frameworks...\n\n     I MUST say that mintiest is *very* readable / understandable\n     compared to the 'other two' options we looked at. Nicely done and\n     thank you for helping us keep our mental sanity.\"\n\n    -- Wayne E. Seguin\n\n\
-  minitest/unit is a small and incredibly fast unit testing framework.\n\
-  It provides a rich set of assertions to make your tests clean and\n\
-  readable.\n\n\
-  minitest/spec is a functionally complete spec engine. It hooks onto\n\
-  minitest/unit and seamlessly bridges test assertions over to spec\n\
-  expectations.\n\n\
-  minitest/benchmark is an awesome way to assert the performance of your\n\
-  algorithms in a repeatable manner. Now you can assert that your newb\n\
-  co-worker doesn't replace your linear algorithm with an exponential\n\
-  one!\n\n\
-  minitest/mock by Steven Baker, is a beautifully tiny mock object\n\
-  framework.\n\n\
-  minitest/pride shows pride in testing and adds coloring to your test\n\
-  output. I guess it is an example of how to write IO pipes too. :P\n\n\
-  minitest/unit is meant to have a clean implementation for language\n\
-  implementors that need a minimal set of methods to bootstrap a working\n\
-  test suite. For example, there is no magic involved for test-case\n\
-  discovery.\n\n    \"Again, I can\xE2\x80\x99t praise enough the idea of a testing/specing\n     framework that I can actually read in full in one sitting!\"\n\n    -- Piotr Szotkowski"
+description: |-
+  minitest provides a complete suite of testing facilities supporting
+  TDD, BDD, mocking, and benchmarking.
+  
+      "I had a class with Jim Weirich on testing last week and we were
+       allowed to choose our testing frameworks. Kirk Haines and I were
+       paired up and we cracked open the code for a few test
+       frameworks...
+  
+       I MUST say that mintiest is *very* readable / understandable
+       compared to the 'other two' options we looked at. Nicely done and
+       thank you for helping us keep our mental sanity."
+  
+      -- Wayne E. Seguin
+  
+  minitest/unit is a small and incredibly fast unit testing framework.
+  It provides a rich set of assertions to make your tests clean and
+  readable.
+  
+  minitest/spec is a functionally complete spec engine. It hooks onto
+  minitest/unit and seamlessly bridges test assertions over to spec
+  expectations.
+  
+  minitest/benchmark is an awesome way to assert the performance of your
+  algorithms in a repeatable manner. Now you can assert that your newb
+  co-worker doesn't replace your linear algorithm with an exponential
+  one!
+  
+  minitest/mock by Steven Baker, is a beautifully tiny mock object
+  framework.
+  
+  minitest/pride shows pride in testing and adds coloring to your test
+  output. I guess it is an example of how to write IO pipes too. :P
+  
+  minitest/unit is meant to have a clean implementation for language
+  implementors that need a minimal set of methods to bootstrap a working
+  test suite. For example, there is no magic involved for test-case
+  discovery.
+  
+      "Again, I can't praise enough the idea of a testing/specing
+       framework that I can actually read in full in one sitting!"
+  
+      -- Piotr Szotkowski
 email: 
 - ryand-ruby@zenspider.com
 executables: []