Re: Proposal: Add signals test_setup and test_teardown to Django test suite runner

Cool, thanks On Sep 20, 3:30 pm, Carl Meyer wrote: > Thanks for your work on this! The usual Django workflow doesn't > include patches to the mailing list: rather you can go ahead and open > a Trac ticket and attach the patch there (even if you aren't sure of > the

Re: Proposal: Add signals test_setup and test_teardown to Django test suite runner

Hi Jim, On Sep 19, 1:19 am, "Jim D." wrote: > I found some time this evening to work this out, and have included a > revised patch for this proposal at the end of this message. Thanks for your work on this! The usual Django workflow doesn't include patches to the mailing

Re: Proposal: Add signals test_setup and test_teardown to Django test suite runner

I found some time this evening to work this out, and have included a revised patch for this proposal at the end of this message. I tried to keep changes to an absolute minimum, but here are a few notes about the changes and decisions I did make: * The addition of this feature required what I

Re: Proposal: Add signals test_setup and test_teardown to Django test suite runner

Thanks for the suggestions and guidance Russ. I'll work with it a bit more and see if it pans out. My main concern with this working smoothly in the core has to do with when and how application code is loaded in the process of setting up tests. It turns out the earliest we can realistically send

Re: Proposal: Add signals test_setup and test_teardown to Django test suite runner

On Sat, Sep 18, 2010 at 12:49 AM, Jim D. wrote: > I recently asked a question on Django Users related to executing > certain code during the global setup and teardown routines that run in > Django's test runner. In my particular use case, I was looking for a > hook where I

Proposal: Add signals test_setup and test_teardown to Django test suite runner

I recently asked a question on Django Users related to executing certain code during the global setup and teardown routines that run in Django's test runner. In my particular use case, I was looking for a hook where I could disable some third party API code when tests execute, in much the same way