transactional-factories 0.1.1 → 0.1.2

data/README.rdoc

@@ -8,21 +8,25 @@ transactional-factories provides self.setup and self.teardown callbacks that are
 
   require 'transactional_factories'
 
-  class MyTest < Test::Unit::TestCase
+  class MyModelTest < Test::Unit::TestCase
+    # Class method setup is called only once to create test data.
     def self.setup
       100.times { MyModel.create }
     end
-    
-    def test_my_model_1
-      assert_equal 100, MyModel.create
+
+    # Instance method setup is called before each test method (usual ruby behavior).
+    def setup
       MyModel.create
-      assert_equal 101, MyModel.create
     end
-    
-    def test_my_model_2
-      assert_equal 100, MyModel.create
-      MyModel.create
-      assert_equal 101, MyModel.create
+
+    def test_1
+      assert_equal 101, MyModel.count
+      MyModel.delete_all
+      assert_equal 0, MyModel.count
+    end
+
+    def test_2
+      assert_equal 101, MyModel.count
     end
   end
 
@@ -32,7 +36,7 @@ transactional-factories provides self.setup and self.teardown callbacks that are
 
 <b>>= ActiveRecord 2.3.x</b> - I don't think ActiveRecord supported nested transactions until 2.3.x.
 
-<b>use_transactional_fixtures = false</b> - Your test cases can not use transactional fixtures.  They're doing about the same thing that the transactional-factories gem is doing and they stomp on each other. 
+<b>use_transactional_fixtures = false</b> - Your test cases can not use ActiveRecord transactional fixtures.  Transactional fixtures wrap each test method in a transaction in such a way that does not allow nesting.  Boo!
 
 If you get this: TransactionalFactories::TransactionalFixturesEnabled, it's time to disable transactional fixtures doing something like this:
 

data/Rakefile

@@ -5,11 +5,12 @@ begin
   require 'jeweler'
   Jeweler::Tasks.new do |gem|
     gem.name = "transactional-factories"
-    gem.summary = "Using nested-transactions to initialize test data programmatically."
-		gem.description = "Transactional-factories uses nested-transactions (like transactional fixtures) to allow efficient initialization of test data programmatically (unlike transactional fixtures)."
+		gem.summary = "Using nested-transactions to allow efficient, programmatic initialization of test data"
+		gem.description = gem.summary
     gem.email = "tim.harrison@yahoo.com"
     gem.homepage = "http://github.com/heedspin/transactional-factories"
     gem.authors = ["Tim Harrison"]
+    gem.add_dependency('activesupport', '>= 2.3.2')
     gem.add_dependency('activerecord', '>= 2.3.2')
     gem.files.exclude '.gitignore'
   end

data/VERSION

@@ -1 +1 @@
-0.1.1
+0.1.2

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: transactional-factories
 version: !ruby/object:Gem::Version 
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors: 
 - Tim Harrison
@@ -9,9 +9,19 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-12-31 00:00:00 -08:00
+date: 2010-01-02 00:00:00 -08:00
 default_executable: 
 dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: activesupport
+  type: :runtime
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: 2.3.2
+    version: 
 - !ruby/object:Gem::Dependency 
   name: activerecord
   type: :runtime
@@ -22,7 +32,7 @@ dependencies:
       - !ruby/object:Gem::Version 
         version: 2.3.2
     version: 
-description: Transactional-factories uses nested-transactions (like transactional fixtures) to allow efficient initialization of test data programmatically (unlike transactional fixtures).
+description: Using nested-transactions to allow efficient, programmatic initialization of test data
 email: tim.harrison@yahoo.com
 executables: []
 
@@ -68,7 +78,7 @@ rubyforge_project:
 rubygems_version: 1.3.5
 signing_key: 
 specification_version: 3
-summary: Using nested-transactions to initialize test data programmatically.
+summary: Using nested-transactions to allow efficient, programmatic initialization of test data
 test_files: 
 - test/db/schema.rb
 - test/lib/blog_post.rb