I am getting TransactionManagementError when trying to save a Django User model instance and in its post_save signal, I’m saving some models that have the user as the foreign key.
Is there a function that is fired at the beginning/end of a scenario of tests? The functions setUp and tearDown are fired before/after every single test.
Is it possible to get the results of a test (i.e. whether all assertions have passed) in a tearDown() method? I’m running Selenium scripts, and I’d like to do some reporting from inside tearDown(), however I don’t know if this is possible.
How to write tests where conditions like the following arise:
I have two files
I am using pythons mock.patch and would like to change the return value for each call.
Here is the caveat:
the function being patched has no inputs, so I can not change the return value based on the input.
Often I’ll write a test class that uses a pytest fixture in every method. Here’s an example. I’d like to be able to avoid having to write the fixture name in the signature of every method. It’s not DRY. How can this be done?
i’m starting the TDD development attitude and am writting unit-tests for my django application. I’m aware of fixtures and know that’s the way tests should be executed, but for a given test i do need to execute it on the whole database, and json fixture for 10+ million row database is not something i’d like to handle, moreover, this test is “read-only”.
In setUp() method of unittest I’ve setup some self variables, which are later referenced in actual tests. I’ve also created a decorator to do some logging. Is there a way in which I can access those self variables from decorator?