I see. Not sure yet if we'll agree that monkey-patching `Date.now()` is the right way to go to get better test coverage. But if we resort to it, then we could increase the time and check it.

Another option is to expose a utility function that takes in a timestamp for what date it is performing the collection. The regular non-test usage would simply pass in `Date.now()` (or maybe it defaults to that), and the tests can specify dates in the future to try and cover future / past dates a bit better.

However, depending on what gets changed wrt the timezone issue that currently stands, there might be another way to do it.