My service has long running processes. For example - user can signup, but if email not verified after 7 days, we send a reminder email.
I need my system test to cover this scenario as well.
Currently, I manipulate the data in the DB so the system thinks the user signed up a week ago.
But this makes my tests tightly coupled with the model and the code itself and the developers.
Is there a better way to handle this?