You might be interested in the Faker gem that will create data for you in all kinds of formats.
On Sun, Apr 11, 2010 at 4:55 PM, Grary <[email protected]> wrote: > Thanks guys. > > What's strange to me is the idea that Rails testing is not > comprehensive, i.e., there are constants, e.g., zip codes, that you > will use in production that you didn't have access to in testing. > While I appreciate that testing is built on cases and not exhaustive, > I can think of situations in my developing app where I might like to > check for "surprises" and I won't want contrived cases derived from > fixtures or factories. I guess what I'm getting at here is the idea > that testing might involve statistical checks, e.g., what is the > probability that I get some certain result? If I get many low > probability results, maybe something's wrong with my constants or the > way I'm handling them, e.g., zip codes. Anyway, this concern straddles > the line between uncertainty about inputs, e.g., app constant data > like zip codes, and outputs -- what an app does with them. > > Thanks for your comments, I consider my question well answered. > > Grar > > On Apr 11, 4:46 pm, Anthony Crumley <[email protected]> wrote: > > Grar, > > > > My recommendation would be to not pre-populate with a migration. I would > > create a ruby script for that and have developers run that script to get > > setup. Then I would run that script in the test/test_helper.rb setup or > > where ever is appropriate if I wanted that data available in my tests. > > > > A more conventional approach would be to create fixtures with the test > > data. Then you can load those fixtures into your development database > with > > "rake db:fixtures:load". > > > > Anthony Crumleyhttp://commonthread.com > > > > On Sat, Apr 10, 2010 at 8:59 AM, Grary <[email protected]> wrote: > > > Hi, > > > > > I'd like to have the results of a migration file that prepopulates my > > > development database available for testing. So, right now, after the > > > usual rake migration, I can access my prepopulated data via script/ > > > console, but not in my unit tests. I've reviewed comments on this > > > subject but the custom rake tasks do not work or attempting a fix with > > > RAILS_ENV=test rake db:migrate as a command does not help either. Any > > > suggestion on how I can get the results of my migration available in > > > the test environment? > > > > > Thanks, > > > > > Grar > > > > > -- > > > 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]<rubyonrails-talk%[email protected]> > <rubyonrails-talk%[email protected]<rubyonrails-talk%[email protected]> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/rubyonrails-talk?hl=en. > > > > > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > -- 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.
