Popular posts

I thought about those approaches

1. make it blocking so you don't need the timeframe (write a process mock functions those are just calls to your api in a specific sequence in the end, as long as you don't need to write to much extra behaviour it should be rather close)
2. make a database watchdog/listener/endlessloop use a callback define a timeout like <median-threshold> seconds and wait for the callback to trigger the assert and end the loop.

In theory you could test the different integrations between the parts of your software as well

if a -> b works and b -> c works and c -> d works
a -> b -> c -> d also works

maybe just keeping the state of the sequences withing the integration test but than you would need to keep the test sequence in order. or you move in the function it depends if you're doing it OOP or FP I guess.

i am just thinking out loud here, I guess most of these thought already crossed your mind. hope this helps at least little.