'ASP.NET - configuring a feature so QA can test it

I'm building a feature in our ASP.NET application where the feature is simply a background service that runs and deletes some old data. I'm using a System.Timers.Timer to run the service every 12 hours.

My question is, how can I build this so that QA can properly test the feature? Obviously I cannot expect QA to wait 12 hours to ensure the feature works.

Some ideas:

  • Have the timer elapsed configurable in a config file.
  • Have some hidden page that QA could load that would run the feature.
  • Have the timer configured differently for QA builds (e.g. run every 15 secs on QA builds)

What's a good way to do this?



Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source