well, I found my problem - sounds like its different from what you're explaining though David. My problem was this... I added a test and decided to piggyback off an existing fixture. I also changed my rake script momentarily to only test my new test when I ran "rake test_mysql". I found I had to add this at the top of my file: require 'fixtures/Developer' require 'fixtures/Project' Then when I switched the rake script back to testing everything - it threw up because those files were already loaded. Not being a ruby expert (yet), is there a way to require it only if it's not already loaded.
Also, I have checked out a pristine copy of the trunk which I will use to do my sanity testing and make sure nothing that's checked in is broken instead of pinging the list (I've done that a couple of times now) - so you shouldn't hear anything more from me like, "you guys sure this works?" Thanks, Ben On 12/14/05, David Heinemeier Hansson <[EMAIL PROTECTED]> wrote: > > Thanks for the sanity check, Jeremy - I'll have to investigate further. > > I've seen the problem too. Then I ran aaa_create_tables.rb by hand, > then it all passed. Please do investigate and see if you can make it > work the first time without this manual step. Thanks! > -- > David Heinemeier Hansson > http://www.loudthinking.com -- Broadcasting Brain > http://www.basecamphq.com -- Online project management > http://www.backpackit.com -- Personal information manager > http://www.rubyonrails.com -- Web-application framework > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core > _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
