lawrencepit-machinery 0.5.1 → 0.5.2

data/README.markdown

@@ -20,6 +20,8 @@ A DataMapper abstraction should be too easy.
 Usage
 -----
 
+#### Object Graphs
+
 In /spec/scenarios.rb
 
     Machinery.define do
@@ -61,16 +63,61 @@ In /spec/models/ship_spec.rb
     end
 
 
-Explain
--------
+#### Just the speed up please
+
+If it's only speeding up your tests you're after you can use anonymous scenarios, like this:
+
+In /spec/models/ship_spec.rb
+
+    describe Ship do
+      scenario do
+        @pirate = Ship.create!(:name => "Pirate")
+      end
+
+      it "should update a pirate ship" do
+        @pirate.name = "Updated Pirate"
+        @pirate.save
+        @pirate.reload
+        @pirate.name.should == "Updated Pirate"
+      end
+
+      it "should have 1 ship" do
+        Ship.count.should == 1
+      end
+
+      it "should be named 'Pirate'" do
+        @pirate.name.should == "Pirate"
+      end
+    end
+
+This will create one ship only in the database.
+
 
-When you use +scenario+ with a block you are defining a scenario. Any instance variables you declare within a scenario will be available in your test.
 
-When you use +scenario+ without a block then you indicate that the block for the scenario you previously defined should be executed. Note that you can re-use scenarios within scenarios.
+Explain
+-------
 
-When you declare to use a scenario within an rspec +ExampleGroup+ (as in the 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.
+When you use +scenario+ with a block you are defining a scenario. Any instance
+variables you declare within a scenario will be available in your test when you
+use that scenario.
+
+When you use +scenario+ without a block then you indicate that the block for the
+scenario you previously defined should be executed. Any instance variables you
+defined within the block will now be available to you in your test methods. Note
+that you can re-use scenarios within scenarios.
+
+When you declare to use a scenario within an rspec +ExampleGroup+ (as in the first
+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.
+
+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
+a named scenario *and* it is used immediately.
+At most one anonymous +scenario+ per example group can be used.
 
 
 Magic?

data/lib/machinery.rb

@@ -50,7 +50,8 @@ module Machinery
 
   module ExampleGroupMacros
     def scenario(*names, &block)
-      Machinery.scenario(names.first, &block) and return if block_given?
+      scenario(:__anonymous__, &block) and scenario(:__anonymous__) and return if names.empty?
+      Machinery.scenario(names.first, &block) and return true if block_given?
       self.before(:all)  { scenarios(*names) }
       self.after(:all)   { rollback_scenarios }
       self.before(:each) { clone_instance_variables }

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: lawrencepit-machinery
 version: !ruby/object:Gem::Version 
-  version: 0.5.1
+  version: 0.5.2
 platform: ruby
 authors: 
 - Lawrence Pit