On 7/29/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > So what advantages are there to the mocking approach over just replacing > the setting?
Genuine mocking (as opposed to this proposal) has one really big advantage - it's lightning fast. All the db-calls get faked using a cache-like setup, so it takes pretty much no time to run any db query. The cost comes in keeping the mock data source up to date. I've been mentally ruminating on adding a mock framework to speed up Django's tests, with some support framework to make generating the mock data easier. When my ideas have congealed a little bit, I might have some code to throw around. Watch this space. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
