Make the test compatible with --processes

RESOLVED WONTFIX

Status

Marketplace
General
P5
normal
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: tarek, Assigned: tarek)

Tracking

x86
Mac OS X
Points:
---

Details

(Assignee)

Description

6 years ago
The tests are slow to execute - and it seems doable to have our test compatible with nose's processes option, which runs several processes in parallel

will need to tweak the sql connection
Won't the multiple processes not quite work with the database which runs each test in transactions? I'd think you'd need multiple databases to run tests in multiple processes?

Also, there's this in Django 1.4, which I haven't played with. Seems like an answer:
https://docs.djangoproject.com/en/dev/topics/testing/#live-test-server
(Assignee)

Comment 2

6 years ago
Yes that the bug I had when I gave it a shot. 

thanks for the link - looks quite interesting.
-> Tarek because this sounds awesome :)
Assignee: nobody → tarek
Target Milestone: --- → 2012-10-04
(Assignee)

Comment 4

6 years ago
one approach that might work is described here: http://www.tomaz.me/2011/04/03/making-django-and-twisted-tests-faster.html

That's not with nose though - but the idea could be refactored in django-nose by writing a django-specific multiprocess plugin that would let us configure "groups of tests" and define which ones we want to run in parallel

I am going to give this a small try to see if it goes anywhere.
(Assignee)

Updated

6 years ago
Priority: -- → P5
Target Milestone: 2012-10-04 → ---

Comment 5

5 years ago
Any update on this or has it been abandoned in favor of just making our tests run faster?

Comment 6

5 years ago
Marking this as WONTFIX since the untangling of TestCases is basically going to involve a complete rewrite of all of our tests. Someday it might make sense to test each app separately (perhaps in its own LXC), but that won't be able to happen until we've done some major refactoring.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.