resque_spec icon indicating copy to clipboard operation
resque_spec copied to clipboard

RSpec matcher for Resque

Results 34 resque_spec issues
Sort by recently updated
recently updated
newest added

Bumps [sinatra](https://github.com/sinatra/sinatra) from 2.0.4 to 3.0.4. Changelog Sourced from sinatra's changelog. 3.0.4 / 2022-11-25 Fix: Escape filename in the Content-Disposition header. #1841 by Kunpei Sakai 3.0.3 / 2022-11-11 Fix: fixed...

dependencies

Bumps [tzinfo](https://github.com/tzinfo/tzinfo) from 1.2.5 to 2.0.5. Release notes Sourced from tzinfo's releases. v2.0.5 Changed DateTime results to always use the proleptic Gregorian calendar. This affects DateTime results prior to 1582-10-15...

dependencies

Bumps [rack](https://github.com/rack/rack) from 2.0.6 to 2.2.3. Changelog Sourced from rack's changelog. Changelog All notable changes to this project will be documented in this file. For info on how to format...

dependencies

Bumps [rake](https://github.com/ruby/rake) from 12.3.1 to 13.0.1. Changelog *Sourced from [rake's changelog](https://github.com/ruby/rake/blob/master/History.rdoc).* > === 13.0.1 > > ==== Bug fixes > > * Fixed bug: Reenabled task raises previous exception on...

dependencies

Hello. In our company we use `Resque.set_scheduler` method and we use your gem, I have found that there is lack of testing for it. I added those methods and rspec...

I want to skip usage of ResqueSpec for some special test case using with `without_resque_spec` block option. `Job.set(...).perform_later` causes ResqueSpec.enqueue_at_with_queue_without_resque_spec method I've found 2 places, that as for me should...

How do we set the expectation that the worker is currently processing a job ? Can we stub the `perform `method, delay and validate ?

I had to run some A/B testing on my project sending some emails at specific time and others at a specific interval, but then I ran into the issue of...

I needed to test some of my resque failure code, but I realized that Resque::Job#fail is not actually run if you are using inline. I think using ResqueSpec.inline simplifies testing...