canonical-django team mailing list archive
-
canonical-django team
-
Mailing list archive
-
Message #00029
Re: Django testing best practices
On Mon, 14 Jun 2010 13:31:03 +0200, Jamu Kakar <jamshed.kakar@xxxxxxxxxxxxx> wrote:
> Well, regardless of whether or not Django commits, you want to make
> sure each test starts with the database in a known state, right? We
> make sure to flush our stores at the end of a test, to make sure
> that SQL statements get to the database to exercise database
> constraints.
Good ideas. I would hope that the Django TestCase takes care of these
things.
> > I have a related issue of managing things like settings.py in multiple
> > branches.
>
> Doesn't Bazaar just do the right thing, or am I missing something
> here?
Well, I currently don't commit the file, as it is supposed to have local
changes.
Cody showed me a way to have multiple files, so I hope to be able to
provide a file with local overrides that will start to rectify this, but
then you may also hit the issue with that file.
Thanks,
James
Follow ups
References