-
Notifications
You must be signed in to change notification settings - Fork 347
Test case using transaction aren't isolated on the non default databases #286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So it is about transactional_db, right? |
indeed, sorry, should have mentioned it. |
Thanks for notifying us, and bisecting it. Can you come up with a test case, based on the existing ones? |
ah, sorry, I'm confusing terms. |
Will try to get a test case for it though won't be able to work on this before next week. |
That is quite the same though, just another way to mark/express it. |
OK, I've been trying to reproduce the issue but failed. Will try to get a failing test case but it'll be slightly more complex. Edit: I changed the title to reflect this. |
@xordoquy |
@blueyed that's on my todo list. Could find some time to work on this today, I was just reporting back. |
Closing this issue as it's probably no longer relevant. |
This is a regression I have with pytest-django 2.9 - doesn't happen with 2.8. Django is 1.7.1, py.test 2.8.2 and Python 3.4.
Some of my tests are using transactions and aren't run in isolation to each other any longer. They are part of a
unittest.TestCase
.Performing a git bisect, the commit 0ec741b seems to introduce the regression.
This is probably due to the fact that it now only applies rollbacks to Django TestCase and no more with unittest's ones.
The text was updated successfully, but these errors were encountered: