For some time now, my unit testing has been taking a longer than expected time. I have tried to debug it a couple of times without much success, as the delays are before my tests even begin to run....

I am trying to mock a chained call on the Djangos model.Manager() class. For now I want to mock the values() and filter() method. To test that I created a little test project: Create a virtual e...

Currently have a project configured to run coverage via Django's manage command like so: ./manage.py test --with-coverage --cover-package=notify --cover-branches --cover-inclusive --cover-erase ...

My python apps testing is performed on the remote server with command nosetests. I cannot modify the way tests are started nor can I add options to it. I have Django app with tests, but tests are n...

I have django-nose 1.0 installed as the test runner for a Django 1.3.1 project. I'm following the instructions on the pypi page regarding test-only models. Here is my settings.py testrunner config...

I have my tests for a Django application in a tests directory: my_project/apps/my_app/ ├── __init__.py ├── tests │ ├── __init__.py │ ├── field_tests.py │ └── storage_tests.py ├── urls.py ├── utils...

I am getting a bit odd behavior using the override_settings decorator. It basically works when I run the test alone, but won't work if I run the whole testing suite. In this test I am changing the...

I am running simple nose tests on a Django website (code available here). Depending on the order that the CLI commands are issued, I get vastly different results! Looking at many posts, it seems ...

I have a django project that used django-nose. I'd like to add django-celery to the project. I use unit tests. Both django-nose and django-celery need a TEST_RUNNER setting in my settings.py file. ...

With Django's normal test runner, you can drill down to run tests in a specific app, a specific subclass of TestCase, or a specific test within a specific subclass of TestCase. E.g.: ./manage.py ...

I am using django-nose to run my unit tests in django (1.4). TEST_RUNNER = 'django_nose.NoseTestSuiteRunner' Creating the database takes a long time. So I found out putting this in settings.py:...

Very similar to lafagundes question about south migration debug logging, except I'm not using south - I'm using plain Django 1.7 migrations. I'm also using django-nose test runner. When I run mana...

I've successfully installed and configured django-nose with coverage Problem is that if I just run coverage for ./manage.py shell and exit out of that shell - it shows me 37% code coverage. I full...

I'm running into a strange problem that seems to come about from how python unit tests manage their imports and how this relates to the mock package. This is for a django project, using django-nose...

I keep hearing people say about how tests should be simple, maintainable, straightforward, but what happens with code re-usability in unit testing? Let's take for example: def test_some_1(): ......

I'm having trouble getting django-nose running. Per the installation instructions, I installed by: Running pip install django-nose Adding 'django_nose' to INSTALLED_APPS in settings.py (includin...

I'm setting up a directory structure for my Django app to separate functional and unit tests. I am using nose as the test runner for my Django project. At the root of the Django project, I have a ...

I am trying to use Django-nose in my current project, but I can't figure out how to get nose to run my tests. So I started a simple Django 1.4.1 project to get to know nose. But not even on this si...