What is the reason for making fixtures more complicated? I don't see the reason for needing more then one set of fixtures, you could just add more fixtures if you need to test new things.
I think there is value in keeping fixtures straight forward; What you want to do is to model a sensible "test" database with your fixtures. In shopify we decided to model a test database based on a store selling winter sports gear ( homage to snowdevil ). The fixtures are telling different stories on their own. For example the order table has a lot of orders during the christmas months. The fixtures have names like "bobs_birthday_present_order". A lot of bugs are found because our test data is organic and is virtually a fully functioning shopify installation. We find many seemingly unrelated breakage because all the tests work on the same data. I think that this is one of the strengths of the current fixture system. On 12/18/05, Duane Johnson <[EMAIL PROTECTED]> wrote: > Hi, > > I talked with bitsweat about flexible fixtures at RubyConf but > haven't heard much since. The patch accompanying ticket #1911 hasn't > been applied, but it looks like #2292 has. There's been some wishing > for this functionality on the list lately, and just wondered what the > state of things are. > > Duane Johnson > (canadaduane) > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails-core > -- Tobi http://jadedpixel.com - modern e-commerce software http://typo.leetsoft.com - Open source weblog engine http://blog.leetsoft.com - Technical weblog _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
