In general, the CPU utilization of your computer is quite high while a Scenario is running.  Devoting less time to graphic animation of the test execution allows the test complete faster. Use the step below to maximize the speed at which your tests run:

Reduce GUI updates: Under Project->Project Settings->Execution there is a Performance Settings option called "Reduce GUI updates". Selecting this option hides the GUI during execution so the system can focus all of its processing on scheduling of transitions (but you won't be able to watch the TestCases execute).

If  you don't want to use the option above, the following steps can cause a marginal increase in speed and reduce memory usage:

Break up large Scenarios: A single Scenario with many TestCases or with very long TestCases uses more memory than executing multiple Scenarios with fewer/shorter TestCases. Multiple Scenarios can be executed in sequence using a regression test. The only issue here is that signal values are not guaranteed to persist between Scenarios like they do between TestCases. You may have to re-use initialization TestCases between Scenarios in this case.

On the Main toolbar, select a lower Display Refresh Rate.

Close windows that you are not interested in viewing. In particular, viewing TestCases that have a short test step can slow the system significantly. Note that a TestCase window can be closed without affecting the execution of a Scenario. The TestCases can be re-opened easily by double-clicking on the Job in the Scenario.


Related Topics:

Running Scenarios–Memory Usage

Recommended Configuration