pytest best practices are no different than unit testing best practices. It sounds like that's your actual question. If so, you'll have better results searching for unit testing documentation and tutorials. Some thoughts on what you've posted dry_run=True is a yellow flag for me. You should test your actual methods as they will be run in production. You can mock the dependencies, but having a flag that changes the method's behavior for testing just means you aren't testing the method. Yes, you should be making assertions--that's how you know things work. I don't know what you mean by conditions. You will almost certainly be testing any particular method several if not dozens of times. You need to test all its edge cases, failure cases, error cases, and valid cases. pytest has the ability to parameterize tests to make this easier. More on reddit.com

Is there a way to use pytest as a test runner to collect some unit tests but prevent pytest from modifying the test code itself on selected unit tests? As part of a series of unit tests in Python, ... More on stackoverflow.com

TEST, TEST, TEST and then test again. You will know the value of testing when your pipeline breaks for some simple edge case. Use libraries like faker to easily generate fake data based on your schema(make sure to track your seeds). Many semantic layers such as dbt allow you to test before publishing as well. While it may be a pain to get in the habit, catching bugs in a test is a much better feeling than in production. I promise you More on reddit.com

I can't imagine going back to unit-test, pytest is so much cleaner and has more flexible fixture configuration. That said, expect to sink a few hours into configuring pytest perfectly, especially if you want to transition and keep your old tests working. It's definitely worth it if you plan on being a django dev longer term and if your projects aren't too small. More on reddit.com