-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
tests fails on admin but works with default test runner #269
Comments
|
Thanks, I downgraded, but nothing. still the same error. |
It appears that nose imports your modules in a different order than your app does, and the Is this an open-source project, where I can duplicate the issue? Or, can you create a test project that demonstrates it? |
First of all, thank you for your support. The project is not opensource, unfortunately. I tried to comments some of the loading on the init.py but nothing. I clean all the .pyc before every tests and still nothing. At the moment the most reasonable thing to do is to revert the admin/ to admin.py it could be a problem with the django 1.7 branch, but I don't know how to proceed to debug the way nose tests the modules in my app. I think is nose, because with the Django test runner everything works. |
I restored the old admin.py file and I get 127 tests passed. I created again the Nose fail with 128 tests. Why nose run 128 tests when I have only 127? Any idea? |
I believe the A few things to try:
This won't fix the problem (and you'll have to figure out where to import |
Hello, I already posted this error on stackexchange, but maybe is a bug.
I'm working on a Django project and we are doing some refactoring. I "promoted" an
admin.py
module to an admin package and I load all the splitted modules in theadmin/__init__.py
Everything works fine. The admin works as expected, but the tests fail if I use nose as a TestRunner.
If I use the default tests runner everything works.
The list of some of the packages I use:
Nose is runned with the following options:
Above the error:
Any idea?
The text was updated successfully, but these errors were encountered: