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 Russell Keith-Magee, 17 years ago

Triage Stage: UnreviewedAccepted

comment:3 by Nis Jørgensen <nis@…>, 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 anonymous, 17 years ago

Cc: remco@… added

comment:5 by Manoj Govindan <egmanoj@…>, 17 years ago

Cc: egmanoj@… added

comment:6 by simon, 16 years ago

This relates to #8138 which proposes running tests in transactions to speed up the database reset operation.

comment:7 by Karen Tracey, 16 years ago

Resolution: fixed
Status: newclosed

I'm going to call this fixed by r9756/#8138. There is perhaps more to do with speeding things up, but the specific item called out in the initial description here, that is the slowness of django.test.TestCase, was fixed in r9756.

Note: See TracTickets for help on using tickets.
Back to Top