This sounds like an interesting challenge. But, I like to keep my tests super stupid and your hand waving solution hurts my head. What about throwing the tests at a cluster or something?
*hands waving* Buuut, say I was to bite... an easy win would be to take a snapshot at the end of a setup block. In theory, that's all your duplicated creations done with, and each test is then doing something unique? Alex. On Mar 16, 2:54 pm, Xavier Shay <[email protected]> wrote: > Idea: > - Either some sort of profiling, where machinist records object creation > and builds up a library (so first run will be just like normal, second > run will be optimized) -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
