Re: Proposal: Do not use global settings.py when running unit tests

2008-11-03 Thread Siddhi
On Nov 3, 6:30 pm, Carl Meyer <[EMAIL PROTECTED]> wrote: > On Nov 3, 3:24 am, Siddhi <[EMAIL PROTECTED]> wrote: > > > What is needed is a way for a test to specify its environment so that > > it is run in the same environment irrespective of the project > > environment specified in settings.py. >

Re: Proposal: Do not use global settings.py when running unit tests

2008-11-03 Thread Carl Meyer
On Nov 3, 3:24 am, Siddhi <[EMAIL PROTECTED]> wrote: > What is needed is a way for a test to specify its environment so that > it is run in the same environment irrespective of the project > environment specified in settings.py. This doesn't fix the third-party/contrib apps problem, but "a way fo

Re: Proposal: Do not use global settings.py when running unit tests

2008-11-03 Thread Calvin Spealman
+1 On Mon, Nov 3, 2008 at 3:24 AM, Siddhi <[EMAIL PROTECTED]> wrote: > > So here is the situation: > > I have a middleware installed that looks at the HTTP_HOST header and > stores the domain and subdomain into the request object. Now when > running unit tests, the tests fail because the HTTP_HOS

Proposal: Do not use global settings.py when running unit tests

2008-11-03 Thread Siddhi
So here is the situation: I have a middleware installed that looks at the HTTP_HOST header and stores the domain and subdomain into the request object. Now when running unit tests, the tests fail because the HTTP_HOST header is not passed into the test Client object. Even if I modify my own tests