Starting a Celery instance and starting the tests should be one command. This could ether be achieved by creating a directive for the Makefile that starts a Celery worker before testing and stops it afterwards even when testing encounters errors.
Or the tests them self could spawn a Celery worker when it is required. This would have the added benefit of clearly differentiating between those parts of the app that require Celery and those who don't.
Starting a Celery instance and starting the tests should be one command. This could ether be achieved by creating a directive for the
Makefilethat starts a Celery worker before testing and stops it afterwards even when testing encounters errors.Or the tests them self could spawn a Celery worker when it is required. This would have the added benefit of clearly differentiating between those parts of the app that require Celery and those who don't.