>> At my day job, with 1,700 test cases in just one project, we are very >> sensitive >> to the quality of our fixtures and their database hooks. Doing things The >> Merb >> Way would slow down both our programming, and our test runs
> I'm sorry? No, doing things the "Merb Way" would NOT slow you down. You > are doing things wrong. Plain and simple. You are refusing to use the > correct tools for the job and then complaining about it. I need you to focus: Writing fixtures in blocks to the database, and using a transaction around each test case is a best practice. Sorry to trigger a diatribe; I'm aware that the Merb community is very good at finding alternatives. One of them is extra complex fixture systems, redundantly declared... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
