database_cleaner 0.5.0 → 0.6.0.rc.1

data/Gemfile.lock

@@ -0,0 +1,145 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    ZenTest (4.3.3)
+    activerecord (2.3.8)
+      activesupport (= 2.3.8)
+    activesupport (2.3.8)
+    addressable (2.2.0)
+    bson (1.0.4)
+    builder (2.1.2)
+    columnize (0.3.1)
+    couch_potato (0.3.0)
+      couchrest (>= 0.24)
+      json
+    couchrest (1.0.1)
+      json (>= 1.4.6)
+      mime-types (>= 1.15)
+      rest-client (>= 1.5.1)
+    cucumber (0.8.5)
+      builder (~> 2.1.2)
+      diff-lcs (~> 1.1.2)
+      gherkin (~> 2.1.4)
+      json_pure (~> 1.4.3)
+      term-ansicolor (~> 1.0.4)
+    data_objects (0.10.2)
+      addressable (~> 2.1)
+    datamapper (1.0.0)
+      dm-aggregates (= 1.0.0)
+      dm-constraints (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-migrations (= 1.0.0)
+      dm-serializer (= 1.0.0)
+      dm-timestamps (= 1.0.0)
+      dm-transactions (= 1.0.0)
+      dm-types (= 1.0.0)
+      dm-validations (= 1.0.0)
+    diff-lcs (1.1.2)
+    dm-aggregates (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-constraints (1.0.0)
+      dm-core (~> 1.0.0)
+      dm-migrations (~> 1.0.0)
+    dm-core (1.0.0)
+      addressable (~> 2.1)
+      extlib (~> 0.9.15)
+    dm-do-adapter (1.0.0)
+      data_objects (~> 0.10.1)
+      dm-core (~> 1.0.0)
+    dm-migrations (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-serializer (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+    dm-sqlite-adapter (1.0.0)
+      dm-do-adapter (~> 1.0.0)
+      do_sqlite3 (~> 0.10.2)
+    dm-timestamps (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-transactions (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-types (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+      stringex (~> 1.1.0)
+      uuidtools (~> 2.1.1)
+    dm-validations (1.0.0)
+      dm-core (~> 1.0.0)
+    do_sqlite3 (0.10.2)
+      data_objects (= 0.10.2)
+    durran-validatable (2.0.1)
+    extlib (0.9.15)
+    fastercsv (1.5.3)
+    gemcutter (0.6.1)
+    gherkin (2.1.5)
+      trollop (~> 1.16.2)
+    git (1.2.5)
+    jeweler (1.4.0)
+      gemcutter (>= 0.1.0)
+      git (>= 1.2.5)
+      rubyforge (>= 2.0.0)
+    jnunemaker-validatable (1.8.4)
+      activesupport (>= 2.3.4)
+    json (1.4.6)
+    json_pure (1.4.6)
+    linecache (0.43)
+    mime-types (1.16)
+    mongo (1.0.7)
+      bson (>= 1.0.4)
+    mongo_mapper (0.8.2)
+      activesupport (>= 2.3.4)
+      jnunemaker-validatable (~> 1.8.4)
+      plucky (~> 0.3.1)
+    mongoid (1.9.1)
+      activesupport (<= 3.0.0)
+      bson (~> 1.0.1)
+      durran-validatable (>= 2.0.1)
+      mongo (~> 1.0.1)
+      will_paginate (< 2.9)
+    plucky (0.3.4)
+      mongo (~> 1.0.7)
+    rake (0.8.7)
+    rcov (0.9.8)
+    rest-client (1.6.0)
+      mime-types (>= 1.16)
+    rspec (1.3.0)
+    ruby-debug (0.10.3)
+      columnize (>= 0.1)
+      ruby-debug-base (~> 0.10.3.0)
+    ruby-debug-base (0.10.3)
+      linecache (>= 0.3)
+    rubyforge (2.0.4)
+      json_pure (>= 1.1.7)
+    sqlite3-ruby (1.3.1)
+    stringex (1.1.0)
+    term-ansicolor (1.0.5)
+    trollop (1.16.2)
+    tzinfo (0.3.22)
+    uuidtools (2.1.1)
+    will_paginate (2.3.14)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  ZenTest
+  activerecord (= 2.3.8)
+  bundler
+  couch_potato (= 0.3.0)
+  cucumber
+  datamapper (= 1.0.0)
+  dm-migrations (= 1.0.0)
+  dm-sqlite-adapter (= 1.0.0)
+  jeweler
+  json_pure
+  mongo_mapper (= 0.8.2)
+  mongoid (= 1.9.1)
+  rake
+  rcov
+  rspec
+  ruby-debug
+  sqlite3-ruby
+  tzinfo (= 0.3.22)

data/History.txt

@@ -1,4 +1,46 @@
-0.5.x (In Git)
+== 0.6.x (In Git)
+
+== 0.6.0 2010-08-2x - The Multi-ORM/Connection Release
+
+This release has the often asked for functionality of being able to clean
+multiple databases within the same project.  This involves being able to 
+clean databases managed by the same ORM (i.e. different connections) and
+also being able to clean databases managed by distinct ORMs.  So, for
+example you can now use DatabaseCleaner on a project that has ActiveRecord
+and Mongoid to help ensure all DBs all in a clean state.  Please see the
+README for more information.  The old API has been preserved so this release
+is backwards compatible.
+
+This release is a result of Jon Rowe's hard work. Many thanks to Jon for all
+of the hours and effort he put into making this feature request a reality.
+
+ === New Features
+  * Ability to clean multiple database connections managed by the same ORM. (Jon Rowe)
+  * Ability to clean multiple DBs managed by different ORMs in same project. (Jon Rowe)
+  * Allows for the ActiveRecord config file (database.yml) to contain ERB and process it. (Fletcher Nichol)
+  * Mysql2Adapter support. (Kamal Fariz Mahyuddin and John Ferlito)
+
+ === Bugfixes
+  * Updates the DataMapper truncation strategy to version 0.10.3. (Robert Rouse)
+
+== 0.5.2
+
+ === Bugfixes
+  * Removes extraneous puts call from configuration.rb.  (Ben Mabey)
+
+== 0.5.1 - The Mongoid Release
+
+This release also attempts to fix AR for Rails 3 support.  I have seen mixed reviews on this.  Some people
+claim the fixes allow for use in Rails3 while others have not had good luck with it.  I plan on reworking
+the way AR support is added so that it is more friendly with how Rails 3 uses autoload.
+
+ === New features
+  * Clean and clean_with methods are now aliased to clean! and clean_with!. (Ben Mabey)
+  * Mongoid Support! (Sidney Burks)
+
+=== Bugfixes
+  * Check PostgreSQL version >= 8.2 before using TRUNCATE CASCADE (James B. Byrne)
+  * Correct superclass is used in ActiveRecord connection adapters. (johnathan, Aslak Hellesoy, Ben Mabey)
 
 == 0.5.0 2010-02-22 - The CouchPotato Release
 

data/README.textile

@@ -5,7 +5,7 @@ The original use case was to ensure a clean state during tests.  Each strategy
 is a small amount of code but is code that is usually needed in any ruby app
 that is testing with a database.
 
-ActiveRecord, DataMapper, MongoMapper and CouchPotato are supported.
+ActiveRecord, DataMapper, MongoMapper, Mongoid, and CouchPotato are supported.
 
 h2. How to use
 
@@ -76,7 +76,55 @@ end
 
 For use in Cucumber please see the section below.
 
+h2. How to use with multiple ORM's
 
+Sometimes you need to use multiple ORMs in your application. You can use DatabaseCleaner to clean multiple ORMs, and multiple connections for those ORMs.
+
+<pre>
+  #How to specify particular orms
+  DatabaseCleaner[:active_record].strategy = :transaction
+  DatabaseCleaner[:mongo_mapper].strategy = :truncation
+  
+  #How to specify particular connections
+  DatabaseCleaner[:active_record,{:connection => :two}]
+</pre>
+
+Usage beyond that remains the same with DatabaseCleaner.start calling any setup on the different configured connections, and DatabaseCleaner.clean executing afterwards.
+
+Configuration options
+
+<table>
+<tr>
+<th>ORM</th>
+<th>How to access</th>
+<th>Notes</th>
+</tr>
+<tr>
+<td>Active Record</td>
+<td>DatabaseCleaner[:active_record]</td>
+<td>Connection specified as :symbol keys, loaded from config/database.yml</td>
+</th>
+<tr>
+<td>Data Mapper</td>
+<td>DatabaseCleaner[:data_mapper]</td>
+<td>Connection specified as :symbol keys, loaded via Datamapper repositories</td>
+</th>
+<tr>
+<td>Mongo Mapper</td>
+<td>DatabaseCleaner[:mongo_mapper]</td>
+<td>Multiple connections not yet supported</td>
+</th>
+<tr>
+<td>Mongoid</td>
+<td>DatabaseCleaner[:mongoid]</td>
+<td>Multiple connections not yet supported</td>
+</th>
+<tr>
+<td>Couch Potato</td>
+<td>DatabaseCleaner[:couch_potato]</td>
+<td>Multiple connections not yet supported</td>
+</tr>
+</table>
 
 h2. Why?
 

data/Rakefile

@@ -1,3 +1,7 @@
+require "rubygems"
+require "bundler"
+Bundler.setup
+
 require 'rake'
 
 begin

data/TODO

@@ -0,0 +1,3 @@
+Could be more Datamapper
+MongoMapper multiple db support
+CouchDB multiple db support

data/VERSION.yml

@@ -1,5 +1,6 @@
 --- 
-:minor: 5
-:build: 
+:minor: 6
 :patch: 0
+:build: 
 :major: 0
+

data/examples/Gemfile

@@ -0,0 +1,46 @@
+source "http://rubygems.org"
+# group :development do
+#   # gem "mysql"
+#   # gem "json_pure", "1.4.3"
+# 
+# 
+#   # gem "datamapper",        "1.0.0"
+#   # gem "dm-migrations",     "1.0.0"
+#   # gem "dm-sqlite-adapter", "1.0.0"
+#   
+#   # mongo requirements
+#     # gem "mongo",     "1.0.1"
+#     # gem "mongo_ext", "0.19.3"
+#     # gem "bson_ext",  "1.0.1"
+# end
+
+group :development do
+  gem "rake"
+  gem "ruby-debug"
+  
+  gem "bundler"
+  gem "jeweler"
+  
+  gem "json_pure"
+  
+  #ORM's
+  gem "activerecord",         "2.3.8"
+  gem "datamapper",           "1.0.0"
+    gem "dm-migrations",      "1.0.0"
+    gem "dm-sqlite-adapter",  "1.0.0"
+  gem "mongoid",              "1.9.1"
+    gem "tzinfo",             "0.3.22"
+  gem "mongo_mapper",         "0.8.2"
+  gem "couch_potato",         "0.3.0"
+end
+
+group :test do
+  gem "rspec"
+  gem "rcov"
+  gem "ZenTest"
+end
+
+group :cucumber do
+  gem "cucumber"
+  gem 'sqlite3-ruby'
+end

data/examples/Gemfile.lock

@@ -0,0 +1,145 @@
+GEM
+  remote: http://rubygems.org/
+  specs:
+    ZenTest (4.3.3)
+    activerecord (2.3.8)
+      activesupport (= 2.3.8)
+    activesupport (2.3.8)
+    addressable (2.2.0)
+    bson (1.0.4)
+    builder (2.1.2)
+    columnize (0.3.1)
+    couch_potato (0.3.0)
+      couchrest (>= 0.24)
+      json
+    couchrest (1.0.1)
+      json (>= 1.4.6)
+      mime-types (>= 1.15)
+      rest-client (>= 1.5.1)
+    cucumber (0.8.5)
+      builder (~> 2.1.2)
+      diff-lcs (~> 1.1.2)
+      gherkin (~> 2.1.4)
+      json_pure (~> 1.4.3)
+      term-ansicolor (~> 1.0.4)
+    data_objects (0.10.2)
+      addressable (~> 2.1)
+    datamapper (1.0.0)
+      dm-aggregates (= 1.0.0)
+      dm-constraints (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-core (= 1.0.0)
+      dm-migrations (= 1.0.0)
+      dm-serializer (= 1.0.0)
+      dm-timestamps (= 1.0.0)
+      dm-transactions (= 1.0.0)
+      dm-types (= 1.0.0)
+      dm-validations (= 1.0.0)
+    diff-lcs (1.1.2)
+    dm-aggregates (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-constraints (1.0.0)
+      dm-core (~> 1.0.0)
+      dm-migrations (~> 1.0.0)
+    dm-core (1.0.0)
+      addressable (~> 2.1)
+      extlib (~> 0.9.15)
+    dm-do-adapter (1.0.0)
+      data_objects (~> 0.10.1)
+      dm-core (~> 1.0.0)
+    dm-migrations (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-serializer (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+    dm-sqlite-adapter (1.0.0)
+      dm-do-adapter (~> 1.0.0)
+      do_sqlite3 (~> 0.10.2)
+    dm-timestamps (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-transactions (1.0.0)
+      dm-core (~> 1.0.0)
+    dm-types (1.0.0)
+      dm-core (~> 1.0.0)
+      fastercsv (~> 1.5.3)
+      json_pure (~> 1.4.3)
+      stringex (~> 1.1.0)
+      uuidtools (~> 2.1.1)
+    dm-validations (1.0.0)
+      dm-core (~> 1.0.0)
+    do_sqlite3 (0.10.2)
+      data_objects (= 0.10.2)
+    durran-validatable (2.0.1)
+    extlib (0.9.15)
+    fastercsv (1.5.3)
+    gemcutter (0.6.1)
+    gherkin (2.1.5)
+      trollop (~> 1.16.2)
+    git (1.2.5)
+    jeweler (1.4.0)
+      gemcutter (>= 0.1.0)
+      git (>= 1.2.5)
+      rubyforge (>= 2.0.0)
+    jnunemaker-validatable (1.8.4)
+      activesupport (>= 2.3.4)
+    json (1.4.6)
+    json_pure (1.4.6)
+    linecache (0.43)
+    mime-types (1.16)
+    mongo (1.0.7)
+      bson (>= 1.0.4)
+    mongo_mapper (0.8.2)
+      activesupport (>= 2.3.4)
+      jnunemaker-validatable (~> 1.8.4)
+      plucky (~> 0.3.1)
+    mongoid (1.9.1)
+      activesupport (<= 3.0.0)
+      bson (~> 1.0.1)
+      durran-validatable (>= 2.0.1)
+      mongo (~> 1.0.1)
+      will_paginate (< 2.9)
+    plucky (0.3.4)
+      mongo (~> 1.0.7)
+    rake (0.8.7)
+    rcov (0.9.8)
+    rest-client (1.6.0)
+      mime-types (>= 1.16)
+    rspec (1.3.0)
+    ruby-debug (0.10.3)
+      columnize (>= 0.1)
+      ruby-debug-base (~> 0.10.3.0)
+    ruby-debug-base (0.10.3)
+      linecache (>= 0.3)
+    rubyforge (2.0.4)
+      json_pure (>= 1.1.7)
+    sqlite3-ruby (1.3.1)
+    stringex (1.1.0)
+    term-ansicolor (1.0.5)
+    trollop (1.16.2)
+    tzinfo (0.3.22)
+    uuidtools (2.1.1)
+    will_paginate (2.3.14)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  ZenTest
+  activerecord (= 2.3.8)
+  bundler
+  couch_potato (= 0.3.0)
+  cucumber
+  datamapper (= 1.0.0)
+  dm-migrations (= 1.0.0)
+  dm-sqlite-adapter (= 1.0.0)
+  jeweler
+  json_pure
+  mongo_mapper (= 0.8.2)
+  mongoid (= 1.9.1)
+  rake
+  rcov
+  rspec
+  ruby-debug
+  sqlite3-ruby
+  tzinfo (= 0.3.22)

data/examples/config/database.yml

@@ -0,0 +1,7 @@
+--- 
+two: 
+  adapter: sqlite3
+  database: /Users/bmabey/Programming/ruby/database_cleaner/examples/features/support/../../db/activerecord_two.db
+one: 
+  adapter: sqlite3
+  database: /Users/bmabey/Programming/ruby/database_cleaner/examples/features/support/../../db/activerecord_one.db

data/examples/config/database.yml.example

@@ -0,0 +1,8 @@
+#This is an example of what database.yml *should* look like (when I wrote it)
+#The real database.yml is generated automatically by the active record model lib (so it can be correct)
+two: 
+  adapter: sqlite3
+  database: /path/to/examples/features/support/../../db/activerecord_two.db
+one: 
+  adapter: sqlite3
+  database: /path/to/examples/features/support/../../db/activerecord_one.db

data/examples/features/example_multiple_db.feature

@@ -0,0 +1,23 @@
+Feature: example
+ In order to test DataBase Cleaner
+ Here are some scenarios that rely on the DB being clean!
+
+  # Background:
+  #   Given I have setup DatabaseCleaner to clean multiple databases
+  #
+  Scenario: dirty the db
+    When I create a widget in one db
+     And I create a widget in another db
+    Then I should see 1 widget in one db
+     And I should see 1 widget in another db
+
+  Scenario: assume a clean db
+    When I create a widget in one db
+    Then I should see 1 widget in one db
+     And I should see 0 widget in another db
+
+  Scenario: assume a clean db
+    When I create a widget in another db
+    Then I should see 0 widget in one db
+     And I should see 1 widget in another db
+

data/examples/features/example_multiple_orm.feature

@@ -0,0 +1,22 @@
+Feature: example
+ In order to test DataBase Cleaner
+ Here are some scenarios that rely on the DB being clean!
+
+ # Background:
+ #   Given I have setup DatabaseCleaner to clean multiple orms
+
+  Scenario: dirty the db
+    When I create a widget in one orm
+     And I create a widget in another orm
+    Then I should see 1 widget in one orm
+     And I should see 1 widget in another orm
+
+  Scenario: assume a clean db
+    When I create a widget in one orm
+    Then I should see 1 widget in one orm
+     And I should see 0 widget in another orm
+
+  Scenario: assume a clean db
+    When I create a widget in another orm
+    Then I should see 0 widget in one orm
+     And I should see 1 widget in another orm

data/examples/features/step_definitions/activerecord_steps.rb

@@ -0,0 +1,31 @@
+Given /^I have setup database cleaner to clean multiple databases using activerecord$/ do
+  #DatabaseCleaner
+  # require "#{File.dirname(__FILE__)}/../../../lib/datamapper_models"
+  #
+  # DatabaseCleaner[:datamapper, {:connection => :one} ].strategy = :truncation
+  # DatabaseCleaner[:datamapper, {:connection => :two} ].strategy = :truncation
+end
+
+When /^I create a widget using activerecord$/ do
+  ActiveRecordWidget.create!
+end
+
+Then /^I should see ([\d]+) widget using activerecord$/ do |widget_count|
+  ActiveRecordWidget.count.should == widget_count.to_i
+end
+
+When /^I create a widget in one db using activerecord$/ do
+  ActiveRecordWidgetUsingDatabaseOne.create!
+end
+
+When /^I create a widget in another db using activerecord$/ do
+  ActiveRecordWidgetUsingDatabaseTwo.create!
+end
+
+Then /^I should see ([\d]+) widget in one db using activerecord$/ do |widget_count|
+  ActiveRecordWidgetUsingDatabaseOne.count.should == widget_count.to_i
+end
+
+Then /^I should see ([\d]+) widget in another db using activerecord$/ do |widget_count|
+  ActiveRecordWidgetUsingDatabaseTwo.count.should == widget_count.to_i
+end

data/examples/features/step_definitions/couchpotato_steps.rb

@@ -0,0 +1,31 @@
+Given /^I have setup database cleaner to clean multiple databases using couchpotato$/ do
+  #DatabaseCleaner
+  # require "#{File.dirname(__FILE__)}/../../../lib/couchpotato_models"
+  #
+  # DatabaseCleaner[:couchpotato, {:connection => :one} ].strategy = :truncation
+  # DatabaseCleaner[:couchpotato, {:connection => :two} ].strategy = :truncation
+end
+
+When /^I create a widget using couchpotato$/ do
+  CouchPotatoWidget.create!
+end
+
+Then /^I should see ([\d]+) widget using couchpotato$/ do |widget_count|
+  CouchPotatoWidget.count.should == widget_count.to_i
+end
+
+When /^I create a widget in one db using couchpotato$/ do
+  CouchPotatoWidgetUsingDatabaseOne.create!
+end
+
+When /^I create a widget in another db using couchpotato$/ do
+  CouchPotatoWidgetUsingDatabaseTwo.create!
+end
+
+Then /^I should see ([\d]+) widget in one db using couchpotato$/ do |widget_count|
+  CouchPotatoWidgetUsingDatabaseOne.count.should == widget_count.to_i
+end
+
+Then /^I should see ([\d]+) widget in another db using couchpotato$/ do |widget_count|
+  CouchPotatoWidgetUsingDatabaseTwo.count.should == widget_count.to_i
+end

data/examples/features/step_definitions/datamapper_steps.rb

@@ -0,0 +1,37 @@
+Given /^I have setup database cleaner to clean multiple databases using datamapper$/ do
+  #DatabaseCleaner
+  # require "#{File.dirname(__FILE__)}/../../../lib/datamapper_models"
+  #
+  # DatabaseCleaner[:datamapper, {:connection => :one} ].strategy = :truncation
+  # DatabaseCleaner[:datamapper, {:connection => :two} ].strategy = :truncation
+end
+
+When /^I create a widget using datamapper$/ do
+  DataMapperWidget.create!
+end
+
+Then /^I should see ([\d]+) widget using datamapper$/ do |widget_count|
+  DataMapperWidget.count.should == widget_count.to_i
+end
+
+When /^I create a widget in one db using datamapper$/ do
+  begin
+    DataMapperWidgetUsingDatabaseOne.create!
+  rescue StandardError => e
+    BREAK = e.backtrace
+    debugger
+    DataMapperWidgetUsingDatabaseOne.create!
+  end
+end
+
+When /^I create a widget in another db using datamapper$/ do
+  DataMapperWidgetUsingDatabaseTwo.create!
+end
+
+Then /^I should see ([\d]+) widget in one db using datamapper$/ do |widget_count|
+  DataMapperWidgetUsingDatabaseOne.count.should == widget_count.to_i
+end
+
+Then /^I should see ([\d]+) widget in another db using datamapper$/ do |widget_count|
+  DataMapperWidgetUsingDatabaseTwo.count.should == widget_count.to_i
+end

data/examples/features/step_definitions/mongoid_steps.rb

@@ -0,0 +1,23 @@
+When /^I create a widget using mongoid$/ do
+  MongoidWidget.create!( :id => rand(1000)+1000)
+end
+
+Then /^I should see ([\d]+) widget using mongoid$/ do |widget_count|
+  MongoidWidget.count.should == widget_count.to_i
+end
+
+When /^I create a widget in one db using mongoid$/ do
+  MongoidWidgetUsingDatabaseOne.create!
+end
+
+When /^I create a widget in another db using mongoid$/ do
+  MongoidWidgetUsingDatabaseTwo.create!
+end
+
+Then /^I should see ([\d]+) widget in one db using mongoid$/ do |widget_count|
+  MongoidWidgetUsingDatabaseOne.count.should == widget_count.to_i
+end
+
+Then /^I should see ([\d]+) widget in another db using mongoid$/ do |widget_count|
+  MongoidWidgetUsingDatabaseTwo.count.should == widget_count.to_i
+end