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

Testing queueing and/or execution of jobs #560

Closed
patbenatar opened this issue Apr 4, 2015 · 5 comments
Closed

Testing queueing and/or execution of jobs #560

patbenatar opened this issue Apr 4, 2015 · 5 comments

Comments

@patbenatar
Copy link
Contributor

I'm not able to find much documentation around the topic of how to test that jobs are added to queues with correct data. It looks like the HTTP API may be useful for getting at this data, but that seems like a roundabout way to get at some testing support. Sidekiq has some nice support for testing: https://github.com/mperham/sidekiq/wiki/Testing#setup ... are there plans on the kue roadmap for adding this sort of functionality? Would you be open to a PR on this topic? Thanks!

@behrad
Copy link
Collaborator

behrad commented Apr 4, 2015

Thank you @patbenatar for the suggestion 👍

are there plans on the kue roadmap for adding this sort of functionality?

not yet

Would you be open to a PR on this topic?

sure yea!

@okor
Copy link

okor commented Apr 5, 2015

I also like this idea 👍

@behrad behrad closed this as completed Apr 22, 2015
@epicbagel
Copy link

Is there a way to process the jobs within test mode? From what I can see in the code, the jobs in the queue aren't processed at all.

@patbenatar
Copy link
Contributor Author

@epicbagel It doesn't currently run the jobs.. We could build a feature similar to Sidekiq's Worker.drain —perhaps kue.drain(jobName)— to manually process any jobs waiting in the queue?

@behrad
Copy link
Collaborator

behrad commented May 13, 2015

a neat PR totally welcomed 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants