On Tue, Sep 21, 2010 at 3:08 PM, Ryan Bigg <radarliste...@gmail.com> wrote: > Cucumber only provides a way to run individual tests through its "cucumber" > executable.
See http://wiki.github.com/aslakhellesoy/cucumber/using-rake require 'cucumber' require 'cucumber/rake/task' Cucumber::Rake::Task.new(:features) do |t| t.cucumber_opts = "--format pretty" end task :features => 'db:test:prepare' > I don't think it should be the responsibility of outside gems or > even the built-in testing frameworks to run rake db:test:prepare before the > tests themselves. It's the responsibility of anyone running tests -- whether test/unit, cucumber, autotest, textmate, etc -- to use the test harness. > The database should be taken care of when you run rake db:migrate for both > the development AND test databases using the criteria I said earlier. The test database is ephemeral. Imagine it is created just before the test run and destroyed just afterward. It is never migrated; it's cloned on the fly *just for that test run.* Anything that expects greater responsibility or longevity from the test db raises red flags and design smells. jeremy -- 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 rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
