• Registered: 2010-07-29
  • Posts: 6

Topic: Testing legacy models, cannot drop tables/views

I'm standing up a very simple rails3 app which provides restful access to some Oracle views. I do not own the dev/test/prod databases - and therefore cannot drop/create/seed the test database when I run test cases.

Basically, I'm just looking to disable the drop/create/seed behavior from Test::Unit.

I've searched google and this forum and the closest thing I've found is this:  http://railsforum.com/viewtopic.php?id=14678  but that's a couple years old, and didn't bear fruit.

Has anyone found their way around this?

  • Registered: 2010-07-29
  • Posts: 6

Re: Testing legacy models, cannot drop tables/views

I should probably tell you what happens when I try to run functional tests:

someone@the_server:~/applications/my_rails_app$ rake test:functionals
(in /applications/my_rails_app)
/applications/my_rails_app/db/schema.rb doesn't exist yet. Run "rake db:migrate" to create it then try again. If you do not intend to use a database, you should instead alter /applications/my_rails_app/config/boot.rb to limit the frameworks that will be loaded

This is interesting. I'm using AR to query the Oracle views, works great. But my testing is inhibited here because Rails doesn't understand that it does not control the database.

Thoughts welcome.