Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Celery #39

Open
martgra opened this issue Jul 6, 2020 · 1 comment
Open

Celery #39

martgra opened this issue Jul 6, 2020 · 1 comment

Comments

@martgra
Copy link

martgra commented Jul 6, 2020

Celery tests not passing with tox or pytest. Probably because no broker/result backend running.
Needs a) update in readme and b) some sort of w/a. Either run tests eager, or spin up an instance to test end to end.

@karec
Copy link
Owner

karec commented Jul 6, 2020

Hello @martgra and thanks for reporting this issue.

For a) I'll add some details to the readme to specify that you need at least a rabbitmq to pass celery tests locally
For b) I think the best solution is to set tasks to always eager by default, and allow override of this setting via env variables, so when running tests inside docker-compose you can actually use rabbitMQ / redis containers for end to end testing

@Lehoczky Lehoczky mentioned this issue Jul 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants