I've broken _hourly a couple times now (including f7e1e24) simply because it lacked even a smoke test, and work on #64 is a little hampered because of this.
I'm thinking there would literally just be a test_events.test_modinit that either monkeypatches time.time or possibly provides a mocked multibot (or just multibot.loop.queue) that just allows the test to advance the time arbitrarily. Though it might be more straightforward in the long term to actually pull most of _hourly into a fully independent function, so the remaining _hourly stub just calls multibot.multical.poll() and _new_independent_hourly(multibot).
I've broken
_hourlya couple times now (including f7e1e24) simply because it lacked even a smoke test, and work on #64 is a little hampered because of this.I'm thinking there would literally just be a
test_events.test_modinitthat either monkeypatchestime.timeor possibly provides a mockedmultibot(or justmultibot.loop.queue) that just allows the test to advance the time arbitrarily. Though it might be more straightforward in the long term to actually pull most of_hourlyinto a fully independent function, so the remaining_hourlystub just callsmultibot.multical.poll()and_new_independent_hourly(multibot).