Re: Schema tests and test_foreign_key_index_long_names_regression

I answer to myself. The implementation of DatabaseIntrospection.get_indexes in django-firebird is so old, It come from of the first version. I fixed it and It works fine now. I was confusing because I was seeing the implementation of oracle backend and also seem like It retrieves just primary

Re: Loading fixtures once for each TestCase to improve running time

In fact, I just reinvented https://code.djangoproject.com/ticket/20392. The patch on that ticket is pretty good, I'll try to review it again. -- Aymeric. On 7 juin 2014, at 10:12, Aymeric Augustin wrote: > Hi Josh, > > Fixtures don't receive a lot of

Re: Loading fixtures once for each TestCase to improve running time

Hi Josh, Fixtures don't receive a lot of attention because they're hard to maintain and generally inferior to object generators such as factory_boy. Still, it would be good to optimize them. On 7 juin 2014, at 09:34, Josh Smeaton wrote: > I've been looking into the

Loading fixtures once for each TestCase to improve running time

I've been looking into the django testing infrastructure today to see if there was any particular reason why the test suite takes so long to run. Mainly, I didn't understand why fixtures are loaded for every single test method. To be honest, I didn't think fixtures were loaded for every test