I am using Selenium tests to continuously probe a website for correctness. These are not tests which are intended to be run after a deployment, but actually test data specific issues where the data is constantly shifting.
Currently the tests are kicked off via TeamCity with a regular cron job and execute in BrowserStack. This feels like an inefficient use of a TeamCity agent which is constantly occupied polling BrowserStack for test results.
Is there a recommended way to schedule Selenium tests or as a Continuous Integration system not a bad option? There are a number of different tests so I'd rather not have a whole load of possibly overlapping scheduled task. Is there an industry standard way of orchestrated probe test execution?