README.rdoc acts_as_versioned.gemspec @@ -1,10 +1,15 @@ [master] + + * +[0.6] + * (23 Dec 2008) Clean up old old code and start move towards new gem [Ken Collins] * Starting a .gitignore file. * Moving to a test/lib based directory structure with a boot and AAV test case based from ActiveRecord's case. * Create rake test and test_dbs tasks. + * Create a gemspec for publishing as a gem. [0.5.2] CHANGELOG @@ -1,42 +1,21 @@ == Creating the test database -The default name for the test databases is "acts_as_versioned_plugin_test". If you -want to use another database name then be sure to update the connection -adapter setups you want to test with in test/connections/<your database>/connection.rb. -When you have the database online, you can import the fixture tables with -the test/fixtures/db_definitions/*.sql files. - -Make sure that you create database objects with the same user that you specified in i -connection.rb otherwise (on Postgres, at least) tests for default values will fail. +The default name for the test databases is can be found in the test/lib/database.yml files. By +default the tests will run on sqlite3 but can be changed using and ENV['DB'] variable like postresql, +mysql or even sqlserver. == Running with Rake -The easiest way to run the unit tests is through Rake. The default task runs -the entire test suite for all the adapters. You can also run the suite on just -one adapter by using the tasks test_mysql_ruby, test_ruby_mysql, test_sqlite, -or test_postresql. For more information, checkout the full array of rake tasks with "rake -T" - -Rake can be found at http://rake.rubyforge.org +The easiest way to run the unit tests is through Rake. The default task runs all the test cases. +There is even a rake task called test_dbs that will run all test cases for each DB. == Running by hand Unit tests are located in test directory. If you only want to run a single test suite, or don't want to bother with Rake, you can do so with something like: - cd test; ruby -I "connections/native_mysql" base_test.rb + cd test ; ruby -I "test" versioned_test.rb -That'll run the base suite using the MySQL-Ruby adapter. Change the adapter -and test suite name as needed. - -== Faster tests - -If you are using a database that supports transactions, you can set the -"AR_TX_FIXTURES" environment variable to "yes" to use transactional fixtures. -This gives a very large speed boost. With rake: - - rake AR_TX_FIXTURES=yes - -Or, by hand: +Likewise you can just hit Command-R if you are using TextMate. - AR_TX_FIXTURES=yes ruby -I connections/native_sqlite3 base_test.rb RUNNING_UNIT_TESTS README c62896de63f6339d008522db7dfe449e99239eb9 Ken Collins ken@metaskills.net http://github.com/xmlblog/acts_as_versioned/commit/001b04e735437da1f788f7ff5243eaa085a9753b 001b04e735437da1f788f7ff5243eaa085a9753b 2008-12-29T09:33:51-08:00 2008-12-29T09:33:51-08:00 Adding a gem spec and pusing a new "me" release for 0.6.0. 23041ee4d46bde8c4d7d5eefed4e4068f0165da1 Ken Collins ken@metaskills.net