GitLab

Celery tasks run on separate processes (possibly on separate machines) known as workers. In most situations, a scalable number of workers is run continuously which runs tasks as they become available. However, for testing, workers will need to be spawned programmatically so that tasks are only run when the results of that task are being observed.

This milestone is considered complete when a wiki page exists for each of the following:

• Document spooling up a local pool of celery workers for development.
• Document any set-up necessary to run the unit tests.
• Document deployment of an AWS EB environment (or similar entity on the AWS stack) that works as a celery worker.