Heya.
My employer is using Django 3.1
I have been running into weird inconsistencies with our testing for a while now.
At this point i have narrowed it down to the database not being rolled back after tests get executed.
I can confirm this by looking at the data as tests are going on.
For example, users get assigned certain objects and these persist between test cases even though they shouldn't.
All of the tests are StaticLiveServerTestCase based.
How would I even go about debugging this?
The documentation clearly states all changes are rolled back, all of the interaction done is purely through the orm, but I have very concrete proof that this doesnt happen.
#StaticLiveServerTestCase not rolling back after test
4 messages · Page 1 of 1 (latest)
In what method are you creating your test data?
within the view functions called when im accessing the subdomain.
our app is quite extensive but none of the data is created through the test case
within the view functions called when im accessing the subdomain.
What does this mean?