<![CDATA[Rails Forum - Ruby on Rails Help and Discussion Forum - Testing with a DB I don't control.]]> http://railsforum.com/viewtopic.php?id=48194 Mon, 12 Mar 2012 12:00:52 +0000 PunBB <![CDATA[Re: Testing with a DB I don't control.]]> http://railsforum.com/viewtopic.php?pid=150695#p150695 May be FactoryGirlRails could help you.

]]> Mon, 12 Mar 2012 12:00:52 +0000 http://railsforum.com/viewtopic.php?pid=150695#p150695 <![CDATA[Testing with a DB I don't control.]]> http://railsforum.com/viewtopic.php?pid=150689#p150689 The Rails framework, for testing, seems to assume that the app creates/defines the
database it uses.  But what about when I'm only *reading* an existing DB? 

Granted, I could write migrations that *approximate* the schema of the existing DB, and then
populate the test DB (again, in an approximate way) in my tests but that's not very helpful.

How do *you* write and run tests when you don't want to erase the test DB?

Thanks,

Mike

]]> Mon, 12 Mar 2012 06:16:38 +0000 http://railsforum.com/viewtopic.php?pid=150689#p150689