How can a Python Unit Test make Linux think more system time has passed than actually has? [on hold]

I have c++ code with internal timers that measure the time between update messages received from a mobile device. After 60 seconds of inactivity, the device is automatically de-registered from my internal database.

Without having to make my unit test wait for 60 seconds, how can I issue a command to the c++ code (via python and UDP sockets) to PRETEND like 60 seconds has elapsed? The platform is on Linux.