My guess is that you'd need to add this to your test setup. By default, everything is rolled back from your test database after every test.
def setup `rake db:seed` end With backticks it will run the shell process, and should wait for it to finish before proceeding. Nothing comes up when I search the api docs for 'seed', so for now it may just be in rake. It may take some digging in the source to find out whether you can seed the database directly from Rails. Or there may be a gem that can help. On Sep 28, 8:20 am, Nathan Beyer <nbe...@gmail.com> wrote: > We've started using seeds.rb to populate some low-level required data > into our database, but we're having some issues with this data getting > removed and not re-entered while running the tests. > > Is seeding part of the testing lifecycle or do we have to replicate > the seed data in the fixtures as well? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
