mirror of
https://github.com/DatabaseCleaner/database_cleaner
synced 2023-03-27 23:22:03 -04:00
6e554cb2d7
Conflicts:
VERSION.yml
features/step_definitions/database_cleaner_steps.rb
lib/database_cleaner/configuration.rb
spec/database_cleaner/active_record/transaction_spec.rb
spec/database_cleaner/configuration_spec.rb
spec/database_cleaner/mongo_mapper/truncation_spec.rb
This is merge is not yet complete. The Mongoid strategy/specs is not completely updated
to the new structure of the project. Additionaly, I see quite a bit of
duplication between Mongoid and MongoMapper. Since they both rely on
the same underlying mongo lib I am thinking of just having a single
Mongo strategy. How the default connection is inferred can use
autodetect magic of MongoMapper and Mongoid. (Meaning, for the
Truncation strategy the #connection method would get the connection
from either MongoMapper or Mongoid depending on what is defined...
or it could use what was set by the user.)
32 lines
468 B
Ruby
32 lines
468 B
Ruby
source "http://rubygems.org"
|
|
group :development do
|
|
gem "mysql"
|
|
gem "json_pure", "1.2.0"
|
|
gem "rspec", "1.3.0"
|
|
gem "cucumber"
|
|
|
|
gem "activerecord"
|
|
|
|
gem "datamapper", "0.10.2"
|
|
gem "data_objects"
|
|
gem "do_sqlite3"
|
|
|
|
gem "mongoid"
|
|
gem "tzinfo"
|
|
gem "mongo_mapper"
|
|
gem "mongo"
|
|
gem "mongo_ext"
|
|
gem "bson_ext"
|
|
|
|
gem "couch_potato"
|
|
|
|
gem "rake"
|
|
gem "ruby-debug"
|
|
gem 'sqlite3-ruby'
|
|
|
|
gem "ZenTest"
|
|
|
|
gem "bundler"
|
|
gem "jeweler"
|
|
end
|
|
|