On 03/30/2014 06:02 AM, Harry Percival wrote: > In that case, maybe the question is: which should be the default? > > Given that, as you say, most people use staticfiles, it feels to me like > the test case in which static files "just work", without having to > remember to run `collectstatic` before each test run, would feel like a > good default. > > More advanced users who are managing their static assets totally > differently -- on a CDN, say -- can then use the more restrictive > LiveServerTestCase if they want to. Although the default test case > would still work just fine for them. > > Maybe there's a parallel with TestCase and TransactionTestCase? The > first will work in 90% of cases, the latter you can use if you have some > more specialised requirements...
What does "default" mean in this case? In what way is one of these more "default" than the other? Neither one is used by the default project template. In terms of code location, it makes sense that the "basic" version lives in core, and the version that relies on contrib.staticfiles extends the core version and lives in contrib.staticfiles. Maybe there's a documentation patch you're thinking of to direct people more clearly to StaticLiveServerTestCase? Currently it looks like that only happens in the "changed in Django 1.7" note at the bottom of that section. Carl
signature.asc
Description: OpenPGP digital signature
