This article discusses the various run execution options available in AppVerify.


After creating test plans in AppVerify, they can be executed in one of three ways:

  • Manually
  • Scheduled
  • Scheduled, but executed manually

Let’s look at each option.


This is just what it sounds like, you generate a test run and then execute it. This is very helpful when you are creating a new test plan so you can test it out before running it “for real”. This is also a good option when you have test plans that only need to be executed infrequently. The downside is you must log into AppVerify, generate or create a test run, and then play it…all manual steps that must be completed every time you want to run the test plan. When playing a manually generated test plan, you cannot choose the robot that will be used for the run.

The really nice thing about manual execution is you can remove test cases and/or processes from the test plan before starting the test run. This is great when you have a test plan with a lot of test cases and you only need to run some of them. You don’t have to create a new test plan, enter variable data, create test cases and add validation actions; just remove the test cases you don’t want to execute after you generate the test run and play it.


Like our manual counterpart, scheduled is just what it sounds like. When you schedule a test run, you can control the days, hours, how many times it runs, what days you don’t want it to run, which test plan (or plans) you want to run and which rTester(s) you want to use. You can create a custom calendar to control when you do and when you don’t want a scheduled run to occur. Once you create your schedule and active it, all that’s left for you to do is go in after the run and review the results.

When building your automation strategy scheduled test executions will be a major player. If you have multiple scheduled runs that all happen to start at the same time or their times overlap, that’s OK. AppVerify will automatically queue any that have to wait for available robots.

Scheduled, but Executed Manually

This allows you to schedule multiple test plans and specify the rTester(s) to use. As an example, this is a good option for your automated system tests. Normally you run these toward the end of the testing cycle for a given release. You can go ahead and set up all the test plans that make us your system testing and select the rTesters. Then, when it is time to do system testing, execute the schedule.

Each option has its advantages; together they give you a robust set of execution options.