Opened 17 years ago
Closed 16 years ago
#4998 closed (fixed)
Database activity makes test cases very slow
Reported by: | Russell Keith-Magee | Owned by: | nobody |
---|---|---|---|
Component: | Testing framework | Version: | dev |
Severity: | Keywords: | ||
Cc: | remco@…, egmanoj@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The level of database activity required by the test system renders the testing process painfully slow. This is especially bad with django.test.TestCase - resets are very expensive operations, which can significantly slow down the testing process (to impractical speeds).
Change History (7)
comment:1 by , 17 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
Just out of curiosity: In my experience, this is a big problem with postgresql, and almost no problem with sqlite (which runs in-memory for tests). How slow are things in the other backends?
comment:4 by , 17 years ago
Cc: | added |
---|
comment:5 by , 17 years ago
Cc: | added |
---|
comment:6 by , 16 years ago
This relates to #8138 which proposes running tests in transactions to speed up the database reset operation.
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
discussion is here