Home/ Questions/Q 3987312
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T06:07:07+00:00

my Django tests run really slowly, but it’s not the test’s fault. At the

  • 0

my Django tests run really slowly, but it’s not the test’s fault.

At the moment, the whole process takes 14s, but only 0.1s of that is running tests. The first few seconds are creating tables & indexes, the rest is applying the project’s many fixtures.

What’s the best way to deal with this? I think there is a way of specifying which fixtures to load in each test, but I need most of them to do most tests…

A solution I think would work is if the tests didn’t drop the tables after each run, that way there would be no need to create & populate the database each run-through of the tests. Most tests don’t even write to the DB.

What’s the best way to optimise the fixture-loading part of Django tests?
Thanks!

(I’m using nose, but otherwise just plain Django and sqlite)

EDIT: I should have mentioned that I’m using an in-memory sqlite database. What I’m looking for – specifically – is an optimisation of the fixture-loading section of the test.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    “but I need most of them to do most tests”…

    Sorry about this, but to speed things up you’re going to have to do some thinking.

    “I think there is a way of specifying which fixtures to load in each test”

    This is a disturbing thing to read. Have you looked at your tests recently?

    Your tests do — specifically — list the fixtures. You need to minimize that list.

    • 0