-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Documentation for mocking in case of testing #7
Comments
It shouldn't be too hard to add something like that. I'll give it some thought and get back to you. |
Great. If you also write how to use pdb inside of workers - it will be really good for us. |
It's been a long day and I committed this straight to master. |
As far as debugging; since everything runs inside a Django context, you can just debug like you would debug your own applications in Django. |
Great, Thank you! |
Greetings.
I've found this library quite interesting, but to start using it (as I follow TDD) it would be really convenient to know how to make asynchronous execution synchronous in case of testing (like CELERY_ALWAYS_EAGER). A friend of mine dropped rq as it was really hard to write tests for tasks code there.
The text was updated successfully, but these errors were encountered: