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

Test trigger acquisition logic #14

Open
lukeryannetnz opened this issue Oct 30, 2016 · 1 comment
Open

Test trigger acquisition logic #14

lukeryannetnz opened this issue Oct 30, 2016 · 1 comment

Comments

@lukeryannetnz
Copy link
Owner

The core logic around which triggers to fire, including the cluster locking/scheduler logic is contained in two large, complex methods:
AcquireNextTriggers
ApplyMisfireIfNecessary

We need decent test coverage over these to assert they are behaving correctly before we can refactor/change them. It would also be nice to have confidence that the dynamo conditional writes used to implement distributed locks are working as desired.

@lukeryannetnz
Copy link
Owner Author

@ddhi004 if you want a challenge, this requires a fair amount of mental enterprise.

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

1 participant