I'm testing a software system that forces users to take action on their data every 60 or 180 days. The users get notified when the due date is approaching or if they have missed one. These users can also request an extension to the due date.
We can't test this in real-time because the durations are just too long. Right now, I'm struggling with how to test this system within a several week test cycle. I can think of two ways to handle this.
- Have the system trigger action requests every two or three days instead of 60 or 180.
- Become friendly with a system administrator who will change the server clock for me, when I need it.
Are there other approaches to testing this type of scenario? I realize that this isn't a new problem, so I want to learn about how others have handled it.