Applies to TestExecute 14.50, last modified on July 15, 2020

One of the common tasks performed when testing applications is running tests at certain time, for example, every night at 1:00 a.m. To perform this task, you can run TestExecute using any scheduling program and pass the appropriate command-line arguments to it. For instance, you can run TestExecute using the Windows Task Scheduler. A step-by-step instruction on how to do this is below:

Prerequisites for running tests on Windows 8 and later

If you are not going to test Windows Store applications, disable the support for Windows Store applications in TestExecute. To do this, right-click the TestExecute icon () in the notification area (tray), select Options > Engines > General and then clear the Enable support for testing Windows Store applications check box.

Otherwise, to be able to test Windows Store applications, keep the support enabled and create an external script that will run TestExecute. To learn how to do it, see the instructions below.

Create a scheduled task
  1. In your Windows operating system, open the Control Panel. The way you do this depends on the Windows version you use. For example:

    • Windows 10: In the search box on the taskbar, type control panel and then click Control Panel.

    • Windows 8: Move the mouse to the top right corner of the screen to open the Charms bar, then click Search and search for control panel.

    • Windows 7: Click Windows Start button > Control Panel.

  2. In the search box, type schedule, and then select Schedule tasks. This will open the Task Scheduler window.

  3. Click Create task in the Actions panel on the right to create a new scheduled task. This will open the Create Task wizard.

  4. Use the wizard to specify the task properties like name, time, user account and others.

  5. Specify the instructions that will launch TestExecute:

    On Windows 7:

    See instructions

    On Windows 8 and later:

    To test Windows Store applications:

    See instructions

    To test applications other than Windows Store applications:

    See instructions

Notes

  • For complete information on TestExecute command-line arguments, see TestExecute Command Line.

  • Use TestExecute exit codes to determine if the test run was successful. If you need to check whether the test was successful, you can create a batch file which will call TestExecute, specify command-line arguments for it and check TestExecute exit code. You can find an example for this batch file in the TestExecute Exit Codes topic.

  • If the scheduled task has the Run only when user is logged on option, then the machine should NOT be locked at the moment the task is trigged.

    If the scheduled task has the Run whether user is logged on or not option, then the machine could be locked, but, in this case, the TestExecute project should be launched with the /SilentMode command-line parameter.

See Also

TestExecute Command Line
TestExecute Exit Codes

Highlight search results