Defining the Testing Frequency
You can define how often the test should be run by defining a frequency. For example, to ensure your login process works, set the frequency to every hour. You will receive an email if the test fails. Note that when you define a frequency, the test will be run with the default settings for that test. You can run your test at the following intervals:
- On demand - This is the default frequency and means that the test will be run manually.
- 1 Hour
- 2 Hours
- 6 Hours
- 12 Hours
- Daily
- Weekly
- Monthly
This topic discusses:
How the Frequency is Calculated
When you set a testing frequency, Preflight checks the last test time. If the time is longer than the frequency you set, it will run in the next 5 minutes. Otherwise it will run when the period since the last run has elapsed. This is also true if you change the frequency, that is, Preflight waits for the new frequency time.
Example 1: If you have a test that you haven't tested for a while, and you change the frequency to 1 hour, it will run in the next 5 minutes, then it will run an hour after that.
Example 2: If you have a test that you just created and ran, and then set the frequency to 1 hour, it will run after 1 hour.
Example 3: If you have a test that was set to run once a month and it last ran 10 days ago, if you change the frequency to once a week, it will run in the next 5 minutes.
Defining the Frequency
You can define a frequency for a single test in the Test Details tab, or for one or more tests from the All Tests page.
Changing the Frequency from the Test Details Tab
To Change the Frequency for a Single Test
- In the Navigation bar, select Tests.
- Select a specific test to open it.
- Click Test Settings at the top right of the page and select Frequency.
- Select a frequency from the list and click Save.
Changing the Frequency for Multiple Tests
To Change the Frequency for Multiple Tests
-
In the Navigation bar, select Tests.
-
In the All Tests or Groups pages select the tests (using the checkbox on the left).
-
Click the Frequency menu that appears at the top of the screen and select an option.
-
Cick Apply to Selected.
Recommendations
- If you run tests every hour across all of the browsers, you will use up your testing package much quicker. In addition, there is little advantage to testing hourly across browsers.
- It is recommended to test occasionally and on a single browser.
- When deploying new code, it is recommended to test across browsers.
- For smoke tests, use the browser/OS combination your most commonly used by your customers.
- If you've experienced specific issues regarding a particular browser's compatibility changing over time, regular testing is recommended, otherwise, test on one browser.
Related topics
Defining Global Testing Defaults