On 4/5/07, Roderick van Domburg <[EMAIL PROTECTED]> wrote: > been musing that the CI build isn't picking up the failures because > those fixtures are still lingering in the CI databases from earlier > revisions.
activerecortd/test/aaa_create_tables_test.rb is running before everything else (because Unit::Test sorts test classes alphabetically) and it recreates every table in the test database. So, as long as drop and create scripts include all tables used in tests, nothing lingers in the CI databases from a previous build. Besides, I don't get any errors from "rake test_mysql" and "rake test_sqlite3"on fresh, empty databases with or without the patch, anyway. Listing all required fixtures in every test, so that the test can be executed all by itself, is still the right thing to do. -- Alex Verkhovsky --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
