#36496: SQLite test database path not recognised when running tests in parallel
-----------------------------------+--------------------------------------
     Reporter:  Damian Posener     |                    Owner:  (none)
         Type:  Bug                |                   Status:  new
    Component:  Testing framework  |                  Version:  5.2
     Severity:  Normal             |               Resolution:
     Keywords:                     |             Triage Stage:  Unreviewed
    Has patch:  0                  |      Needs documentation:  0
  Needs tests:  0                  |  Patch needs improvement:  0
Easy pickings:  0                  |                    UI/UX:  0
-----------------------------------+--------------------------------------
Comment (by Damian Posener):

 Replying to [comment:3 Simon Charette]:
 > I don't think that's something Django's test machinery claims to
 supports by the way, I can't think of multiple things that would break
 running multiple test suites against the same checkout of a projects.

 We are using Django as a CMS for 14 different websites, and the nature of
 that beast is a lot of separate apps, each with their own separate test
 suites. Being able to run app tests in parallel saves us a bunch of time,
 but this database thing is a bit of a thorn in our side.

 I think there's also some (probably minor) security risks around Django
 simply dumping it's databases copies in the current working directory. For
 one the directory might not actually be writable. If it is writable, it
 may contain other `.sqlite3` files that aren't meant to be overwritten
 (Django does not seem to check whether the DBs are its own and will
 happily overwrite existing ones).

 Personally I'd be happy if there was at least a way to specify where
 Django should store the files, but there seems to be no other option than
 to use the current working dir.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36496#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070197ee565d8a-eceb3dce-b9b6-4cc8-b9bc-de18b38700c2-000000%40eu-central-1.amazonses.com.

Reply via email to