Does Django test methods carry over?

The question of whether Django test methods "carry over" is nuanced and depends on what you mean by "carry over." Let's break it down:

1. Test Methods Within a Test Class:

- In Django, test methods within a `TestCase` class (or any class inheriting from `unittest.TestCase`) do not inherently "carry over" state from one method to another. Each test method is executed in isolation. Django sets up a fresh database for each test method and tears it down afterward. This ensures that tests are independent and don't interfere with each other.

2. Fixtures and Setup:

- If you need to set up data or perform actions that are common to multiple test methods within the same test class, you can use the `setUp` method. This method is executed before each test method. Similarly, the `tearDown` method is executed after each test method. These methods allow you to prepare and clean up the environment for each test, but they don't "carry over" state between test methods.

3. Test Data and Database State:

- While the database is reset for each test method, you can use fixtures or the `setUp` method to create initial data. However, any changes made to the database within one test method will not persist for the next test method. Each test starts with a clean slate.

4. Inheritance of Test Classes:

- If you have a base test class and inherit from it, the test methods in the base class will be executed along with the test methods in the derived class. However, the same rules about isolation apply: each test method, regardless of where it's defined, is executed in isolation.

5. Sharing Data Between Tests (Not Recommended):

- While it's technically possible to share data between tests by using class-level variables or other means, it's generally not recommended. This can lead to tests that are difficult to understand, debug, and maintain. It's better to keep tests isolated and independent.

In Summary:

- Django test methods do not "carry over" state or data between them. Each test method is executed in isolation with a fresh database. Use `setUp` and `tearDown` for setup and cleanup, and avoid sharing data between tests to maintain test integrity and clarity.

Therefore, while you can use setup methods to prepare data, the core principle is that each test method operates independently, ensuring that tests are reliable and predictable.

Learn more about this