LiveServerTestCase vs StaticLiveServerCase

Just updating my book to using the django 1.7 beta. I use LiveServerTestCase a lot. I used to rely on the fact that LiveServerTestCase "magically" serves static files from app folders. I see the default functionality is that this no longer works, but I can get it by switching to

Re: Migrations in Django 1.7 make unit testing models harder

Am just working on updating my book on TDD to django 1.7 based on the beta. Currently half-way thru, not run into any problems because I don't use migrations until a later chapter, but when I do I will run into the same problems Bernie mentions. Will share more once I've finished the

Re: LiveServerTestCase vs StaticLiveServerCase

On Sat, Mar 29, 2014 at 1:26 PM, Harry Percival wrote: > > [...] > > But I just wanted to express the fact that it feels a little > counter-intuitive. I don't know enough to weigh how important it is to > remove a dependency on a contrib app from the testcases

Re: Migrations in Django 1.7 make unit testing models harder

No, there is no way to turn off migrations for tests - some of the core tests won't work without them turned on, in fact, and adding that option would be weird (why only tests? what would it do? how do you load data in now initial_data is gone?). The only complaint I've seen - the one that Bernie

Re: LiveServerTestCase vs StaticLiveServerCase

Well, neither, really, but, if anything, the latter. - I don't think there's any bugs in StaticLiveServerCase. - I have changed all my tests to use the new class. it wasn't the end of the world. What I *am* saying is that, in my opinion, there's not much point in LiveServerTestCase if it

Re: Migrations in Django 1.7 make unit testing models harder

I suspect you're probably right. Having to run makemigrations in between making changes to model code and running tests isn't the end of the world i suppose. Will know better what I'm talking about when I've actually got to that part of the book... On 29 March 2014 18:23, Andrew Godwin

Re: LiveServerTestCase vs StaticLiveServerCase

On Saturday 29 March 2014 19:11:17 Harry Percival wrote: > > What I *am* saying is that, in my opinion, there's not much point in > LiveServerTestCase if it doesn't do static files. So, to keep things > simple, it would be simpler to remove it, and just have on LiveServer test > class, that

Ticket #22355: Humanize timedelta objects in Templates

Hi All, I've created a ticket along with the patch, tests and docs for a filter for humanizing timedelta objects on django templates. Please find the concerned ticket here: https://code.djangoproject.com/ticket/22355 It would be awesome if any of the generous committers could review it and

Re: Migrations in Django 1.7 make unit testing models harder

OK, I've now run into the problem IRL, and sure enough, it's different to what i'm used to. Am trying to overcome my knee-jerk reactions of "why did it change! i hate it!". ignoring that for a moment then: One thing I did find surprising was that I'm going thru TDD in small steps like this:

Re: Migrations in Django 1.7 make unit testing models harder

> > I thought TextField did have a default, the empty string? > > Like every other field, the "default default" is None (NULL). -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from

Re: LiveServerTestCase vs StaticLiveServerCase

On 03/29/2014 02:36 PM, Shai Berger wrote: > On Saturday 29 March 2014 19:11:17 Harry Percival wrote: >> >> What I *am* saying is that, in my opinion, there's not much point in >> LiveServerTestCase if it doesn't do static files. So, to keep things >> simple, it would be simpler to remove it, and