Closed ce07c3 closed 4 years ago
Hi! I pushed a branch validating clockwork test picking up wildcard values in the at:
option. This spec is passing for me.
The tick_speed
might be causing issues for you, though I'd expect that to pick up the job 3 times (at 00:00, 00:300, and 1:00, the three clock ticks you'd get), but I'm not certain/obviously that's not the case.
Perhaps you can use that test case as a guide?
EDIT: here's a link to the test I'm referencing, as the branch referenced above was merged.
Sure, I'll check it out! 👍
Was that commit helpful to you in resolving your issue?
The commit is gone, but I can see the branch was merged and deleted. I'll check off master now.
Still having the same issues.
I've recreated your exact scenario in another branch, given in rspec, not minitest.
There are two commits:
IMO, scenario 2 is a better representation of the scenario you're looking to validate; however either show the job running more than zero times.
Note that also in my clock file I would recommend saying this job runs every minute. While saying it runs every hour works (as evident in these tests), I think it's less clear to see a job run every 10 minutes when it's said to run hourly.
Note that with both scenarios I've created tracking down this issue, I cannot reproduce the issue of Clockwork::Test
not supporting wildcard times.