Will do! Happy to hear that it made sense and that you've made the adjustments to include this functionality in the main branch. This will be super useful for me.

Cool! I’d be interested to hear more about how you’re using Proletarian, if you’re able to share details?

Hey, sure. Will get back to you on this later this week

Hey @U06BEJGKD, wanted to confirm that the test setup works fine here with the latest checkout of proletarian. Nice! As for my use case: So, we use proletarian on the one hand as part of a job-queue of a workflow engine, but also in one slightly different setting, where it kicks off business processes at a certain time on another day. What I want to be able to do is to set up proper acceptance testing for the whole thing. In order to do this I want to test the system against its http server endpoints, treating the system effectively as a black box. The requests and responses from the endpoints I can map to acceptance criteria. Now I want to tell the system that I want to trigger some process, which then also kicks off, as a side effect so to speak, another process which should run on the other day. Then I want to act as if it is that day and ask the system, by querying against a http endpoint again, in which state it is. Given that state I will be able to judge if the process has in fact been kicked off. In summary, I want to test the whole system, and I want to be able to confirm that it handles these kind of asyncronous use cases properly, and I want to "compress" the time such that I can have automated tests.

Cool, that’s some serious whole-system testing!