Russ, Well, as you can tell from my initial post, this was my initial concept. However, you seem to be proposing to launch nosetests from the 'manage.py test' execution rather than directly from the command line. Am I reading you right? Hadn't considered that option. Not sure how much effort it would be so will have to dig into nosetests source to determine. Seems a bit complex at first glance, however.
thanx, -- Ben PS: Meanwhile for the specific model in question, I have moved the fixtures under the test directory itself and have the unit test class explicitly load those fixtures so my monkey-patch can happen prior to the fixture load. Not a general solution but works for now. On Sep 23, 7:55 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > The solution here is easy - write your own custom test runner. The > default Django test runner monkeypatches the mail sending libraries > and the template generation. You need to monkeypatch one of your > internal capabilites, so you will need to write a custom test runner > that does so. I haven't looked at the nosetests test runner, but I'd > be surprised if it can't be substantially reused (or at the very > least, copied) for your own custom test runner. > > 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 -~----------~----~----~----~------~----~------~--~---
