micro_mock 0.0.3 → 0.0.4

data/README.md

@@ -44,6 +44,9 @@ assert_equal 5, count # Test::Unit
 count.should eq 5 # RSpec
 ```
 
+Of course you wouldn't normally test the mock itself... rather the code that uses the mock.
+I'll work on adding some real world examples.
+
 ```ruby
 # create a mock that subclasses Array
 Mock = MicroMock.make(Array)
@@ -54,6 +57,3 @@ list.stub :say_hi do |name|
 end
 list.say_hi "Nate" # => "Hi Nate!"
 ```
-
-Of course you wouldn't normally test the mock itself... rather the code that uses the mock.
-I'll work on adding some real world examples.

data/lib/micro_mock/version.rb

@@ -1,3 +1,3 @@
 module MicroMock
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

data/lib/micro_mock.rb

@@ -66,6 +66,7 @@ module MicroMock
     klass ||= Class.new
     klass.extend MicroMock
     klass.send :include, MicroMock
+    Object.const_set "MicroMock#{klass.object_id}", klass
     klass
   end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: micro_mock
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-11-15 00:00:00.000000000 Z
+date: 2012-11-17 00:00:00.000000000 Z
 dependencies: []
 description: ! '    MicroMock might just be the lightest mocking strategy available.