pytest-dev / pytest-dev/pytest-django

Modifying INSTALLED_APPS with the settings fixture does not update the app registry

Open
#811 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.5k
Forks
367
PR merge metrics
No merged PRs in 30d

Description

I don't have an obvious simple test case ready, but I can try to cook one up later. The gist is that when I wanted to insert a new package to INSTALLED_APPS during tests, I had to use django.test.modify_settings, because just appending a new entry to the settings using the fixture didn't trigger a reload of models, and, by consequence, the models' relation graphs didn't get populated.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by creating a minimal test case that changes INSTALLED_APPS with the settings fixture and compare it with django.test.modify_settings. Check whether the app registry reloads and model relation graphs are populated in both cases; done means the fixture change produces the expected registry state.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.