Skip to main content

Run a monitored Celery worker for integration tests that depend on Celery tasks

Project description

Fork of celerytest with minor bug fixes

celerytest - Integration testing with Celery

Writing (integration) tests that depend on Celery tasks is problematic. When you manually run a Celery worker together with your tests, it runs in a separate process and there’s no clean way to address objects targeted by Celery from your tests. When you use a separate test database (as with Django for example), you’ll have to duplicate configuration code so your Celery worker accesses the same database.

celerytest provides the ability to run a Celery worker in the background from your tests. It also allows your tests to monitor the worker and pause until Celery tasks are completed.

Using celerytest

To start a Celery worker in a separate thread, use:

app = Celery() # your Celery app
worker = start_celery_worker(app) # configure the app for our celery worker

To wait for the worker to finish executing tasks, use:

result = some_celery_task.delay()
worker.idle.wait() # optionally specify time-out

Django

To use this with your django app through django-celery, get your app as such:

from djcelery.app import app
worker = start_celery_worker(app)

TestCase

If you want to use this in a unittest TestCase, you can use CeleryTestCaseMixin. If you’re writing unit tests that depend on a celery worker, though, you’re doing it wrong. For unit tests, you’ll want to mock your Celery methods and test them separately. You could use CeleryTestCaseMixin to write integration tests with Celery tasks, though.

from unittest import TestCase
from celerytest.testcase import CeleryTestCaseMixin, setup_celery_worker
import time

app = Celery()
setup_celery_worker(app) # need to setup worker outside

class SomeTestCase(CeleryTestCaseMixin, TestCase):
    celery_app = app
    celery_concurrency = 4

    def test_something(self):
        result = multiply.delay(2,3)
        self.worker.idle.wait()
        self.assertEqual(result.get(), 6)

Lettuce

To automatically launch a worker in the background while running a Lettuce integration test suite, add to terrain.py:

# my_celery_app.py
app = Celery('my_celery_app', broker='amqp://')

# terrain.py
from lettuce import *
from celerytest import start_celery_worker

# replace this with an import of your actual app
from my_celery_app import app

@before.harvest
def initial_setup(server):
    # memory transport may not work here
    world.celery = start_celery_worker(app, config="amqp")

@after.harvest
def cleanup(server):
    world.celery.stop()

@after.each_step
def after_step(step):
    # make sure we've received any scheduled tasks
    world.celery.active.wait(.05)
    # allow tasks to complete
    world.celery.idle.wait(5)

Installation

Install the latest version of celerytest from PyPI:

$ pip install celerytest

Or, clone the latest version of celerytest from GitHub and run setup:

$ git clone git://github.com/RentMethod/celerytest.git
$ cd celerytest
$ ./setup.py install # as root

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

celery_testutils-0.1.2.tar.gz (6.8 kB view details)

Uploaded Source

Built Distribution

celery_testutils-0.1.2-py2-none-any.whl (8.8 kB view details)

Uploaded Python 2

File details

Details for the file celery_testutils-0.1.2.tar.gz.

File metadata

File hashes

Hashes for celery_testutils-0.1.2.tar.gz
Algorithm Hash digest
SHA256 fa7fe7909398fc7f7b87a7745f5da9d943a31ab5cdd3d3d36c279ab9b43b2690
MD5 9d4226eb5086d34bfbaf1a6fc8fc6105
BLAKE2b-256 f61167546e307a2f42afff0ee456b99a1f805e6456b1be989036a84291fd460f

See more details on using hashes here.

File details

Details for the file celery_testutils-0.1.2-py2-none-any.whl.

File metadata

File hashes

Hashes for celery_testutils-0.1.2-py2-none-any.whl
Algorithm Hash digest
SHA256 05f607f64346754a7a05941498105abfa5bcfb29f50a15c566f1cf07766d9d26
MD5 b26facbb651e3ba9b4e2c4afe97054b2
BLAKE2b-256 d7c1b9d59b7f784d5c58d8510a2891d5af93e715c8404c8f6150aed0017db839

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page