Open skorfmann opened 1 year ago
Yes, I've wondered if we should have some kind of "test" or "tick" or "trigger" or "run" or some other way to manually trigger the scheduled function. It does seem feel like apps using this resource are hard to test at the moment
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 90 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Feature Spec
Make it easy and less verbose to test a
Schedule
Use Cases
To make the inflight handler of a schedule testable, I'll have to define it explicitly like this so that I have a reference to it.
Would be nicer to being able to define it like:
and invoke it with something like
schedule.tick()
orTestHelper.tick(schedule)
.Implementation Notes
No response
Component
No response
Community Notes