Heinz Strunk wrote: > Well, I meant the data from seeds.rb which is not loaded in the test > environment by default. I just db:seed RAILS_ENV=test and commented > fixtures :all out so the seed doesn't get overridden.
As I said, This is a VERY BAD idea. One of the primary rules of testing is to reset your test database between each and every test that runs. You want to start each test (or spec) in a "known state." This is why fixtures work the way they do. But, fixtures are a complete pain to deal with. Machinist is a test data factory framework that is much more maintainable, and sane, than using fixtures. Take the time to read though the docs of the Machinist Github page. And, read up on how to do proper unit testing and you'll see the error of your ways. -- Posted via http://www.ruby-forum.com/. -- 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 [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-talk?hl=en.
