Specifies the number of application instances to be run. If Count is less than 0, the method will run as many instances as the
TestedApp.Count property specifies. If Count is 0, no instances will be run.
||The number of instances to be launched depends on the IgnoreRunning parameter. If this parameter is True, the
Run method launches as many application instances as the Count parameter specifies.
If the IgnoreRunning parameter is False (default), the total number of running instances cannot exceed the value specified by the Count parameter. Suppose, the Count parameter holds seven meaning that TestComplete can run a maximum of seven instances of your tested application. Suppose also, that five instances are already running. In this case, TestComplete will only run two new instances of the tested application (2 + 5 = 7).
The Count parameter is ignored if the Debug or Profile run mode is selected. If Profile mode is selected, TestComplete launches the application under AQtime, so the Count value is meaningless. If Debug mode is active, TestComplete always launches one application instance.
Про демо не упомянуто.
Думаю, что у вас "If Debug mode is active, TestComplete always launches one application instance".
Режимы описаны тут:
When Debug run mode is selected, TestComplete acts as a debugger for the tested application. After it launches the application, it monitors events that occur during the application run and reports information on these events to the test log. The traced events include debug strings sent by the application to the debugger, exceptions, the load and unload of modules and many others (see List of Traced Events).
For each event, TestComplete posts a message with appropriate information to the test log. For instance, if an exception occurs in the application under test, TestComplete posts the exception information to the log along with the stack of function calls that led to the exception (the exception information is added as an error message to the Test log table and the call stack is visible in the Remarks pane when you select this error message).
The Debug run mode is only available if the DbgServices plug-in is installed in TestComplete.
The tracing functionality is controlled by two options located in the DbgServices Options dialog: Enable events and Priority. The Enable events setting turns event tracking on or off. Priority sets the priority attached to the messages posted to the test log of each application event. You can choose a priority level that will distinguish event messages from other messages.
You can also control the DbgServices options from tests through the
||To enable exception tracing, activate the Exceptions | Active option.
In order for TestComplete to be able to include function names and source line numbers in the call stack, the application under test must be compiled with debug information.
Also, note that when using the Debug mode, TestComplete ignores the Count value specified for the tested application (this value specifies the number of application instances TestComplete should run). If the Debug mode is selected, TestComplete always launches one new application instance.
To use the Debug run mode for your tested application, specify Debug in the Run Mode column of the TestedApps editor.
The Debug mode has two parameters that let you specify command-line arguments and a working folder for the application. To configure these parameters, select the Debug run mode in the TestedApps editor, press the ellipsis button in the Parameters cell and use edit boxes of the ensuing Parameters dialog.
You can also activate the Debug mode and specify its parameters from scripts or keyword tests. For more information on this, see Modifying Run-Mode Parameters From Scripts.
For complete information on using the Debug mode, see Tracing Events and Exceptions With Debug Services.
успешный запрос: http://goo.gl/oYLJr