set the following settings: TEST_RUNNER = 'celery.contrib.test_runner.run_tests' Then we can write our actually test in a tests.py somewhere: from django.test import TestCase from myapp.tasks import add failing Answer: If you’re running tests from your Django project, and the celery test suite is failing in that context, then follow the steps below. If the celery tests are failing in another context, please Django is running tests for all applications in INSTALLED_APPS by default is a pet peeve for many. You should use a test runner that either 1. Explicitly lists the apps you want to run tests for, or 2. Make

Documentation, Release 1.0.6 (stable) TEST_RUNNER = ’celery.contrib.test_runner.run_tests’ Then we can write our actually test in a tests.py somewhere: from django.test import TestCase from myapp.tasks import add failing Answer: If you’re running tests from your Django project, and the celery test suite is failing in that context, then follow the steps below. If the celery tests are failing in another context, please Django is running tests for all applications in INSTALLED_APPS by default is a pet peeve for many. You should use a test runner that either 1. Explicitly lists the apps you want to run tests for, or 62 Chapter

– Running the unit test suite – Creating pull requests * Calculating test coverage * Running the tests on all supported Python versions – Building the documentation – Verifying your contribution * pyflakes Stop running the tests at the first test that fails. • -s Don’t capture output • --nologcapture Don’t capture log output. • -v Run with verbose output. If you want to run the tests for a single test test file only you can do so like this: $ nosetests celery.tests.test_worker.test_worker_job 5.6.3 Creating pull requests When your feature/bugfix is complete you may want to submit a pull requests so

5.5 TEST_RUNNER = ’djcelery.contrib.test_runner.CeleryTestSuiteRunner’ Then we can put the tests in a tests.py somewhere: from django.test import TestCase from myapp.tasks import add class AddTestCase(TestCase): – Running the unit test suite – Creating pull requests * Calculating test coverage * Running the tests on all supported Python versions – Building the documentation – Verifying your contribution * pyflakes Stop running the tests at the first test that fails. • -s Don’t capture output • --nologcapture Don’t capture log output. • -v Run with verbose output. If you want to run the tests for a single test

repository Running the unit test suite Creating pull requests Calculating test coverage Running the tests on all supported Python versions Building the documentation Verifying your contribution pyflakes Stop running the tests at the first test that fails. -s Don’t capture output --nologcapture Don’t capture log output. -v Run with verbose output. If you want to run the tests for a single test test file only you can do so like this: $ nosetests celery.tests.test_worker.test_worker_job Creating pull requests When your feature/bugfix is complete you may want to submit a pull requests so that it

settings: TEST_RUNNER = 'djcelery.contrib.test_runner.CeleryTestSuiteRunner' Then we can put the tests in a tests.py somewhere: from django.test import TestCase from myapp.tasks import add class AddTestCase(TestCase): repository Running the unit test suite Creating pull requests Calculating test coverage Running the tests on all supported Python versions Building the documentation Verifying your contribution pyflakes Stop running the tests at the first test that fails. -s Don’t capture output --nologcapture Don’t capture log output. -v Run with verbose output. If you want to run the tests for a single test

– Running the unit test suite – Creating pull requests * Calculating test coverage * Running the tests on all supported Python versions – Building the documentation – Verifying your contribution * pyflakes Stop running the tests at the first test that fails. • -s Don’t capture output • --nologcapture Don’t capture log output. • -v Run with verbose output. If you want to run the tests for a single test test file only you can do so like this: $ nosetests celery.tests.test_worker.test_worker_job 5.6.3 Creating pull requests When your feature/bugfix is complete you may want to submit a pull requests so

repository Running the unit test suite Creating pull requests Calculating test coverage Running the tests on all supported Python versions Building the documentation Verifying your contribution pyflakes Stop running the tests at the first test that fails. -s Don’t capture output --nologcapture Don’t capture log output. -v Run with verbose output. If you want to run the tests for a single test test file only you can do so like this: $ nosetests celery.tests.test_worker.test_worker_job Creating pull requests When your feature/bugfix is complete you may want to submit a pull requests so that it

errors and returns their string representation in the reply. • Functional test suite added celery.tests.functional.case contains utilities to start and stop an embedded celeryd process, for use in functional workers terminated prematurely. • Added Python version trove classifiers: 2.4, 2.5, 2.6 and 2.7 • Tests now passing on Python 2.7. • Task.__reduce__: Tasks created using the task decorator can now be pickled Chapter 9. Change history Celery Documentation, Release 2.0.3 (stable) • setup.py: nose added to tests_require. • Pickle should now work with SQLAlchemy 0.5.x • New homepage design by Jan Henrik Helmers:

issues using Celery with pyparsing 1.4.x, so please upgrade to the latest version. • Lots of new unit tests written, now with a total coverage of 95%. 9.11.3 Fixes • celeryev Curses Monitor: Improved resize properly handles Ctrl+C by simply exiting instead of showing confusing traceback. • Windows: All tests are now passing on Windows. • Remove bin/ directory, and scripts section from setup.py. This means entrypoints. 9.11.4 Experimental • Jython: celeryd now runs on Jython using the threaded pool. All tests pass, but there may still be bugs lurking around the corners. • PyPy: celeryd now runs on PyPy.