About the Test Session Scheduler


The Test Session Scheduler allows you to automate the execution of any configured test session in the Test Library. All users can schedule tests and modify their test schedules. Users with Test Administrator or higher permissions can manage all scheduled tests. Schedules are color-coded to indicate ownership. Your tests are highlighted with cyan and other user's schedules are shaded with gray.

When scheduled tests are running, you can monitor them with the System Status window, with the Real-Time Logs by searching for the verb Schedule, or by reconnecting to the test session.

To schedule a Recurring Test via the Recurring Test Wizard, use the (Shift-Alt-W) hot key.

See the following topics below:

NOTES:

  • A test that has a duration defined on the Session Builder tab or on the Automation Control tab is displayed with the minimum time interval on the schedule. Only tests with a stop time defined within the schedule are displayed with a fixed duration.

  • The scheduler does not perform any validation on scheduled tests or on the condition of the test system. If the test session is invalid because one or more test cases is in need of repair or if a test server is reserved, busy, or otherwise unable to accommodate the test, the test will fail and the cause will be noted in the Real-Time Logs.


NOTE: When you temporarily disable tests, it is not persistent. If you restart the TAS for any reason, such as an upgrade, the tests will not be disabled; the schedules will run again. However, when you pause scheduled tests, it is persistent and if you restart the TAS, they will still stay paused.

NOTE: The label changes depending on your user access:

  • For Super User account, and Show = All Tests, the label displays as: Temporarily Disable All User's Tests

  • For all user accounts, and Show = My Tests, the label displays as: Temporarily Disable My Tests.

 

 


 

NOTES:

  • The TAS is not self-correcting the scheduler timer when the system clock is being changed. You should restart the TAS (not reboot) when changing time zone or adjusting by minutes or hours.

  • When time is set back, there will be no indication in the logs, as the timer mechanism just won't fire until the expected minute occurs. But when the time is set forward, we added RT logs to indicate when minutes are skipped.

  • When time is moved ahead where next minute is within 30s: <system> 2019-05-07 09:32:45 Warning SysAdmin Schedule Time changed by 45s and within 30s of next minute, expected 9:32 skipping ahead to 9:33 and re-syncing. Time is currently 09:32:45 (15s until 09:33:00), TAS expected it to be 09:32, it skips 09:32:00 does nothing at this time and waits for 09:33 to execute the 09:33 minute (skipping 09:32)

  • When time is moved ahead where next minute was > 30s away: <system> 2019-05-07 09:38:11 Warning SysAdmin Schedule Time changed by 131s, expected 9:36 executing at 9:38 and re-syncing. Time is currently 09:38:11, TAS expected it to be 09:36, it executes the 09:38 minute since <= :30, and waits until 09:39:00 to execute the 09:39 minute (Skipping 09:36 and 09:37).

  • When time is moved ahead < 30s: <system> 2019-05-07 09:49:16 Warning SysAdmin Schedule Time changed by 16s, expected and executing 9:49, but still re-syncing. Time is currently 09:49:16, TAS expected it to be 09:49, it executes 09:49 minute and waits for 09:50 for next minute (~45s).

  • When user=sms and Show=All Tests, Export, Import, Delete will include all tests. When user=sms and Show=My Tests, Export, Import, Delete will include sms tests. For any other user, Export, Import, Delete will only include that user's tests.

 


 

Related Topics

  1. Creating a Test Session
  2. Searching the Real-Time Logs
  3. Using the System Status Window