Skip to content

Commit a0d1f80

Browse files
committed
new celery resource
1 parent 22d1c72 commit a0d1f80

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

content/pages/04-web-development/30-celery.markdown

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,16 @@ then dive into these specific Celery tutorials.
8989
He gives an overview of Celery followed by specific code to set up the task
9090
queue and integrate it with Flask.
9191

92+
* [Unit testing Celery tasks](https://www.python-celery.com/2018/05/01/unit-testing-celery-tasks/)
93+
explains three strategies for testing code within functions that Celery
94+
executes. The post concludes that calling Celery tasks synchronously to test
95+
them is the best strategy without any downsides. However, keep in mind that
96+
any testing method that is not the same as how the function will execute
97+
in a production environment can potentially lead to overlooked bugs. There
98+
is also an
99+
[open source Git repository with all of the source code](https://github.com/ZoomerAnalytics/python-celery-unit-testing)
100+
from the post.
101+
92102
* [3 Gotchas for Working with Celery](https://wiredcraft.com/blog/3-gotchas-for-celery/)
93103
are things to keep in mind when you're new to the Celery task queue
94104
implementation.

0 commit comments

Comments
 (0)