lawrencepit-machinery 0.5.2 → 0.5.3

data/README.markdown

@@ -1,7 +1,7 @@
 Machinery
 =========
 
-*Machinery to create object graphs.*
+*Machinery to create object graphs and speed up tests.*
 
 Machinery helps to create object graphs for use in tests without needing
 fixtures, using pure ruby style. These object graphs are easily re-usable
@@ -13,7 +13,7 @@ a before(:all) instead of a before(:each), and at the end of the tests
 all activerecord objects created in the before(:all) will be cleaned up
 automatically.
 
-Machinery currently only works with ActiveRecord.
+Machinery works with plain ruby objects and currently supports ActiveRecord.
 A DataMapper abstraction should be too easy.
 
 
@@ -111,8 +111,9 @@ ship_spec example above) then the instances will be created for you exactly once
 They will automatically be removed from the database after all the tests have run.
 Any instance variables declared within a scenario will be cloned before each test.
 If you make sure you use +use_transactional_fixtures+ then this means:
+
 * speedy tests, because instances are created exactly once for all tests
-* you can mess around with the instance variables any way you like within a test method as before each test they will always be in exactly the same state.
+* you can mess around with the instance variables any way you like within a test method as before each test they will always be in exactly the same initial state.
 
 A special case is when you use an anonymous +scenario+ with a block, specified at the
 top of your tests (as in the second ship_spec example above). It will behave as if it's
@@ -189,8 +190,9 @@ Written by [Lawrence Pit](http://lawrencepit.com).
 Thanks to
 [Machinist](http://github.com/notahat/machinist),
 [ModelStubbing](http://github.com/technoweenie/model_stubbing),
-[Shoulda](http://github.com/thoughtbot/shoulda) and
-[FixtureScenarios](http://errtheblog.com/posts/61-fixin-fixtures)
+[FactoryGirl](http://github.com/thoughtbot/factory_girl),
+[FixtureScenarios](http://errtheblog.com/posts/61-fixin-fixtures) and
+[Hornsby](http://github.com/lachie/hornsby)
 for inspiration.
 
 After using model_stubbing on a relatively large project for over a year I decided

data/lib/machinery/active_record.rb

@@ -1,12 +1,12 @@
 module Machinery
   module ActiveRecord
     @@toys = []
-    @@recording = false
+    @@recording_level = 0
 
     def self.record
-      @@recording = true
+      @@recording_level = @@recording_level + 1
       yield
-      @@recording = false
+      @@recording_level = @@recording_level - 1
     end
 
     def self.clear
@@ -21,7 +21,7 @@ module Machinery
     end
 
     def self.created(obj)
-      @@toys << obj if @@recording
+      @@toys << obj if @@recording_level > 0
     end
 
     module Extensions

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: lawrencepit-machinery
 version: !ruby/object:Gem::Version 
-  version: 0.5.2
+  version: 0.5.3
 platform: ruby
 authors: 
 - Lawrence Pit
@@ -28,6 +28,7 @@ files:
 - lib/machinery/active_record.rb
 has_rdoc: false
 homepage: http://github.com/lawrencepit/machinery
+licenses: 
 post_install_message: 
 rdoc_options: []
 
@@ -48,9 +49,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.2.0
+rubygems_version: 1.3.5
 signing_key: 
 specification_version: 2
-summary: Machinery to create object graphs.
+summary: Machinery to create object graphs and speed up tests.
 test_files: []