Brian Mcardle wrote:
> This is more what I'm aiming for. The application has been live for 8 
> months now, and we have a significant amount of data. I'd love to test 
> on it and see if it breaks, then update our fixtures to take the edge 
> cases into account. After the "one-time", it only has to be run, maybe 
> every month, or two months, but I doubt it will make much difference 
> after the one time.
> 
> Which is different from my original intention of using it in every test 
> run. Thanks for your input Robert!

One great thing about this is that we have this wonderful scripting 
language called Ruby. Ruby is excellent for writing scripts to automate 
things, as it turns out.

I'd suggest creating yourself a set of rake tasks that dumps your data 
out into Yaml fixture files. Then you can create tests (or specs) to run 
though all that data. Granted it will be very slow, but for a one-time, 
or not-very-often run, it might be reasonable.
-- 
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.

Reply via email to