Re: Data Migrations and Testing

There's two balancing forces here - I don't want to delay the release as we always do that, but then again we always make sure we ship correct, not on time. I'll investigate this as much as I can this week, and see if I can get the dump-and-restore-to-fixture stuff working, as I think that's the b

Re: Trac #22343 -- select-for-update in autocommit mode

On Thu, Mar 27, 2014 at 4:20 PM, Shai Berger wrote: > The relevant tests do a select-for-update to verify that the "for update" > clause is, indeed, added; and they happen to run in autocommit mode. They fail > because, under Oracle, in autocommit mode, the automatic commit happens > immediately a

Re: Proposal: Write unit tests for JavaScript

Hi Trey, You may be interested in this: https://code.djangoproject.com/ticket/20436 I've started to work on this last year on DjangoCon Europe, I never manage to finish my work mostly because of my work on thesis and other stuff. Maybe I will finish this ticket this week and you start writing

#5437 Make GDAL optional for GIS test runner

Looking to get a decision on whether GDAL should be a required part of GIS infrastructure, or left out and subject to the various checks implemented in this pull reques t. The ticket in question is here . --

Re: Data Migrations and Testing

Hm, I’m not a core developer, but i wouldn’t prefer the documentation that explains the edge cases. As Russel Keith-Magee already said that Django is a tool that ensures quality. We should definitly make a Ticket and try to clear that thing up before the 1.7 release. I mean this is not a new fea