Comments (7)
Thanks for reporting. To my knowledge, this library has not been tested against database events. I can't say confidently if the issue is with your test or the library.
from clockwork-test.
Again, @SirRawlins, I've never used database events with clockwork, but in looking through the documentation, could the issue be that the test does not have a persisted PublisherSubscriberSyncClock
in the database to check against?
In the test snippet you provided, it looks like you set up EmailPublisher
s, which I'm guessing the job works against, but I don't see any PublisherSubscriberSyncClock
s.
I could be misunderstanding the intended usage with database events, as I've never used them personally. Let me know if that helps at all though.
from clockwork-test.
Thanks for getting back to me.
So the PublisherSubscriberSync class is just a clockwork wrapper for the
EmailPublisher class, I would post a code example but am away from my Mac
for the weekend.
The data generated by FactioryGirl should be sufficient. I think it's
another piece of the puzzle missing.
I can dig deeper in to things, just wanted to check I wasn't doing anything
foolish
I could also refactor my clocks to move away from database events and
handle things in another way.
Appreciate the help.
On 7 Oct 2016 9:55 pm, "Kevin Murphy" [email protected] wrote:
Again, @SirRawlins https://github.com/SirRawlins, I've never used
database events with clockwork, but in looking through the documentation,
could the issue be that the test does not have a persisted
PublisherSubscriberSyncClock in the database to check against?In the test snippet you provided, it looks like you set up EmailPublishers,
which I'm guessing the job works against, but I don't see any
PublisherSubscriberSyncClocks.Again, I could be misunderstanding the intended usage with database
events, as I've never used them personally. Let me know if that helps at
all though.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtiK2tgp_t1jCXGpV7cSQjk2jRO_KTgks5qxrGqgaJpZM4KQ2Qb
.
from clockwork-test.
If you could post a sample/update when you're able to, I'm happy to help so I know where this stands with you and can track it.
I can't say I understand the correlation between PublisherSubscriberSyncClock
and EmailPublisher
as you've described, but if setting the EmailPublisher
is sufficient for the PublisherSubscriberSyncClock
to have events, does the FactoryGirl factory have some default values that set, for example, frequency
/at
/other clockwork values so clockwork adds a clockwork event?
If you run the same setup in a local environment outside of test, can you confirm that the events are triggered?
from clockwork-test.
@SirRawlins how are things going with this? Let me know if you've made any progress or need any feedback.
from clockwork-test.
Hi Kevin, I was hoping to look at this the past couple of days but simply
haven't had time to get back to it
Completely up to you as to whether you keep the issue open or close it off
as can't promise when i will get chance.
Appreciate you following up.
On 12 Oct 2016 6:37 pm, "Kevin Murphy" [email protected] wrote:
@SirRawlins https://github.com/SirRawlins how are things going with
this? Let me know if you've made any progress or need any feedback.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtiK6KnDuLhXYZE3iWPsy38Yi1s5Pn_ks5qzRrKgaJpZM4KQ2Qb
.
from clockwork-test.
I'll close this for now, but should you get the time to take a closer look and need to revisit it, please re-open.
from clockwork-test.
Related Issues (15)
- Load up test events by reading file HOT 3
- clockwork 2.0.1 breaks clockwork-test HOT 7
- Clockwork::DatabaseEvents HOT 1
- Test handler as well as schedule HOT 1
- Test against latest ruby point versions
- Test against ruby 2.5 HOT 2
- Forces `config/clock.rb` HOT 2
- Testing 2 clock instances HOT 3
- Migrating from Timecop to ActiveSupport time travel HOT 4
- Release new version HOT 1
- Speed up runs to progress through time faster than actual duration HOT 1
- Redefining constants HOT 13
- Wildcards for times not supported? HOT 7
- times_run doesn't count when using at: option HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from clockwork-test.