-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
SetUpClass error in FastFixtureTestCase: 'module' object has no attribute 'enter_transaction_management' #226
Comments
FastFixtureTestCase has not been maintained since at least Django 1.6, and there are no tests to ensure it is working as intended. This could be a small fix to sync with Django's evolving transaction support, or could be a complete rewrite. |
Is this issue fixed in django 1.11??? |
@jwhitlock so, I guess that worth remove or rewrite the FastFixtureTestCase. Keeping this class not working at the project don't make sense. I'm using
I see the issue #289, talking about test the source at #258. Is it works? Can I help to test the fix? Please, I don't know where else to run. |
@jklemm I'm sorry, I'm no longer using django-nose for my projects, and have moved on to pytest. I'm relying on the current users of the projects to come up with fixes and test each other's PRs. I'm trying to collect PRs and issues related to this topic under https://github.com/django-nose/django-nose/milestone/5. |
I am using Django 1.8 with MySQL and the latest version of Django-nose pulled from this Github repo. I have used django_nose.FastFixtureTestCase instead of django.test.TestCase (as mentioned in the django-nose docs).
The test.py file in settings folder has this particular django-nose setting:
My test_models.py (init.py contains Testcase imported from FastFixtureTestCase):
Error stack throwing up:
The text was updated successfully, but these errors were encountered: