minitest 2.5.1 → 2.6.0

data/History.txt

@@ -1,3 +1,14 @@
+=== 2.6.0 / 2011-09-13
+
+* 2 minor enhancements:
+
+  * Added specify alias for it and made desc optional.
+  * Spec#must_be and #wont_be can be used with predicates (metaskills)
+
+* 1 bug fix:
+
+  * Fixed Mock.respond_to?(var) to work with strings. (holli)
+
 === 2.5.1 / 2011-08-27
 
 * 2 minor enhancements:

data/README.txt

@@ -1,13 +1,24 @@
 = minitest/{unit,spec,mock,benchmark}
 
 home :: https://github.com/seattlerb/minitest
-rdoc :: http://bfts.rubyforge.org/minitest
+rdoc :: http://docs.seattlerb.org/minitest
 
 == 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.
@@ -32,6 +43,11 @@ 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
+
 == FEATURES/PROBLEMS:
 
 * minitest/autorun - the easy and explicit way to run all your tests.

data/lib/minitest/mock.rb

@@ -93,7 +93,7 @@ module MiniTest
     end
 
     def respond_to?(sym) # :nodoc:
-      return true if @expected_calls.has_key?(sym)
+      return true if @expected_calls.has_key?(sym.to_sym)
       return __respond_to?(sym)
     end
   end

data/lib/minitest/spec.rb

@@ -186,10 +186,12 @@ class MiniTest::Spec < MiniTest::Unit::TestCase
   # write specs don't like class inheritence, so this goes way out of
   # its way to make sure that expectations aren't inherited.
   #
+  # This is also aliased to #specify and doesn't require a +desc+ arg.
+  #
   # Hint: If you _do_ want inheritence, use minitest/unit. You can mix
   # and match between assertions and expectations as much as you want.
 
-  def self.it desc, &block
+  def self.it desc = "anonymous", &block
     block ||= proc { skip "(no tests defined)" }
 
     @specs ||= 0
@@ -235,6 +237,7 @@ class MiniTest::Spec < MiniTest::Unit::TestCase
   # :stopdoc:
   class << self
     attr_reader :name, :desc
+    alias :specify :it
   end
   # :startdoc:
 end
@@ -328,9 +331,13 @@ module MiniTest::Expectations
   #
   #    n.must_be :<=, 42
   #
+  # This can also do predicates:
+  #
+  #    str.must_be :empty?
+  #
   # :method: must_be
 
-  infect_an_assertion :assert_operator, :must_be
+  infect_an_assertion :assert_operator, :must_be, :reverse
 
   ##
   # See MiniTest::Assertions#assert_output
@@ -485,9 +492,13 @@ module MiniTest::Expectations
   #
   #    n.wont_be :<=, 42
   #
+  # This can also do predicates:
+  #
+  #    str.wont_be :empty?
+  #
   # :method: wont_be
 
-  infect_an_assertion :refute_operator, :wont_be
+  infect_an_assertion :refute_operator, :wont_be, :reverse
 
   ##
   # See MiniTest::Assertions#refute_respond_to

data/lib/minitest/unit.rb

@@ -285,12 +285,16 @@ module MiniTest
       assert obj.nil?, msg
     end
 
+    UNDEFINED = Object.new
+    def UNDEFINED.inspect; "UNDEFINED"; end
+
     ##
-    # For testing equality operators and so-forth.
+    # For testing with binary operators.
     #
     #   assert_operator 5, :<=, 4
 
-    def assert_operator o1, op, o2, msg = nil
+    def assert_operator o1, op, o2 = UNDEFINED, msg = nil
+      return assert_predicate o1, op, msg if o2 == UNDEFINED
       msg = message(msg) { "Expected #{mu_pp(o1)} to be #{op} #{mu_pp(o2)}" }
       assert o1.__send__(op, o2), msg
     end
@@ -313,6 +317,20 @@ module MiniTest
       (!stdout || x) && (!stderr || y)
     end
 
+    ##
+    # For testing with predicates.
+    #
+    #   assert_predicate str, :empty?
+    #
+    # This is really meant for specs and is front-ended by assert_operator:
+    #
+    #   str.must_be :empty?
+
+    def assert_predicate o1, op, msg = nil
+      msg = message(msg) { "Expected #{mu_pp(o1)} to be #{op}" }
+      assert o1.__send__(op), msg
+    end
+
     ##
     # Fails unless the block raises one of +exp+
 
@@ -576,13 +594,26 @@ module MiniTest
     #   refute_operator 1, :>, 2 #=> pass
     #   refute_operator 1, :<, 2 #=> fail
 
-    def refute_operator o1, op, o2, msg = nil
-      msg = message(msg) {
-        "Expected #{mu_pp(o1)} to not be #{op} #{mu_pp(o2)}"
-      }
+    def refute_operator o1, op, o2 = UNDEFINED, msg = nil
+      return refute_predicate o1, op if o2 == UNDEFINED
+      msg = message(msg) { "Expected #{mu_pp(o1)} to not be #{op} #{mu_pp(o2)}"}
       refute o1.__send__(op, o2), msg
     end
 
+    ##
+    # For testing with predicates.
+    #
+    #   refute_predicate str, :empty?
+    #
+    # This is really meant for specs and is front-ended by refute_operator:
+    #
+    #   str.wont_be :empty?
+
+    def refute_predicate o1, op, msg = nil
+      msg = message(msg) { "Expected #{mu_pp(o1)} to not be #{op}" }
+      refute o1.__send__(op), msg
+    end
+
     ##
     # Fails if +obj+ responds to the message +meth+.
 
@@ -614,7 +645,7 @@ module MiniTest
   end
 
   class Unit
-    VERSION = "2.5.1" # :nodoc:
+    VERSION = "2.6.0" # :nodoc:
 
     attr_accessor :report, :failures, :errors, :skips # :nodoc:
     attr_accessor :test_count, :assertion_count       # :nodoc:

data/test/test_minitest_mock.rb

@@ -85,6 +85,7 @@ class TestMiniTestMock < MiniTest::Unit::TestCase
 
   def test_respond_appropriately
     assert @mock.respond_to?(:foo)
+    assert @mock.respond_to?('foo')
     assert !@mock.respond_to?(:bar)
   end
 

data/test/test_minitest_spec.rb

@@ -89,11 +89,16 @@ describe MiniTest::Spec do
     proc { 42.must_be_nil }.must_raise MiniTest::Assertion
   end
 
-  it "needs to verify using any operator" do
+  it "needs to verify using any binary operator" do
     41.must_be(:<, 42).must_equal true
     proc { 42.must_be(:<, 41) }.must_raise MiniTest::Assertion
   end
 
+  it "needs to verify using any predicate" do
+    "".must_be(:empty?).must_equal true
+    proc { "blah".must_be(:empty?) }.must_raise MiniTest::Assertion
+  end
+
   it "needs to catch an expected exception" do
     @assertion_count = 2
 
@@ -150,6 +155,11 @@ describe MiniTest::Spec do
     proc { "blah".wont_match(/\w+/) }.must_raise MiniTest::Assertion
   end
 
+  it "needs to verify using any (negative) predicate" do
+    "blah".wont_be(:empty?).must_equal false
+    proc { "".wont_be(:empty?) }.must_raise MiniTest::Assertion
+  end
+
   it "needs to verify non-nil" do
     42.wont_be_nil.must_equal false
     proc { nil.wont_be_nil }.must_raise MiniTest::Assertion
@@ -271,6 +281,9 @@ class TestMeta < MiniTest::Unit::TestCase
           before { before_list << 3 }
           after  { after_list  << 3 }
           it "inner-it" do end
+
+          it      {} # ignore me
+          specify {} # anonymous it
         end
       end
     end
@@ -322,11 +335,13 @@ class TestMeta < MiniTest::Unit::TestCase
     assert_equal "very inner thingy", z.desc
 
     top_methods = %w(test_0001_top_level_it)
-    inner_methods = %w(test_0001_inner_it)
+    inner_methods1 = %w(test_0001_inner_it)
+    inner_methods2 = inner_methods1 +
+      %w(test_0002_anonymous test_0003_anonymous)
 
-    assert_equal top_methods,   x.instance_methods(false).sort.map {|o| o.to_s }
-    assert_equal inner_methods, y.instance_methods(false).sort.map {|o| o.to_s }
-    assert_equal inner_methods, z.instance_methods(false).sort.map {|o| o.to_s }
+    assert_equal top_methods,   x.instance_methods(false).sort.map(&:to_s)
+    assert_equal inner_methods1, y.instance_methods(false).sort.map(&:to_s)
+    assert_equal inner_methods2, z.instance_methods(false).sort.map(&:to_s)
   end
 
   def test_setup_teardown_behavior

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: minitest
 version: !ruby/object:Gem::Version 
-  hash: 25
+  hash: 23
   prerelease: 
   segments: 
   - 2
-  - 5
-  - 1
-  version: 2.5.1
+  - 6
+  - 0
+  version: 2.6.0
 platform: ruby
 authors: 
 - Ryan Davis
@@ -36,7 +36,7 @@ cert_chain:
   FBHgymkyj/AOSqKRIpXPhjC6
   -----END CERTIFICATE-----
 
-date: 2011-08-27 00:00:00 Z
+date: 2011-09-13 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: hoe
@@ -53,33 +53,26 @@ dependencies:
         version: "2.12"
   type: :development
   version_requirements: *id001
-description: |-
-  minitest provides a complete suite of testing facilities supporting
-  TDD, BDD, mocking, and benchmarking.
-  
-  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.
+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"
 email: 
 - ryand-ruby@zenspider.com
 executables: []
@@ -139,7 +132,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: bfts
-rubygems_version: 1.8.9
+rubygems_version: 1.8.10
 signing_key: 
 specification_version: 3
 summary: minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking