The Network Suite functionality is deprecated. We don’t recommend using it for distributed testing. Consider using a CI/CD system for managing distributed tests. See Migrating Distributed Tests to CI/CD Systems for details. In case you need to run web tests on multiple environments in parallel, you can also try using your project’s Execution Plan. |
When a distributed test is being executed, it passes through several stages. Some of them are executed consecutively, while others occur only when particular conditions are met. In TestComplete the states of the network suite indicate the stages of the performed distributed test, as well as the states of underlying jobs and tasks. At that, the network suite states of a master project reflect both the states of master and slave projects, while the slave projects only show their state.
During the execution of a distributed test you can monitor the current stage in the Run State page of a master project. If the Activate the Run State page when running tasks option is enabled, TestComplete automatically displays the page when you start the network suite, job or task run.
At run-time, the current state can be obtained in tests via the
NetworkSuite.State
, Job.State
and Task.State
properties. Each of these properties have the same set of return values, but the NetworkSuite.State
indicates the current state of the entire distributed test, whereas the Job.State
and Task.State
represent the state of corresponding job or task.
The following states are possible:
State | Constant Name | Constant Value | Description |
---|---|---|---|
Copying results | ns_CopyingResults |
0 | The task is copying its execution results from a remote computer to the computer where the master project resides.
This state is only applicable to tasks. |
Idle | ns_Idle |
1 | The network suite / job / task is being idle. |
Initializing | ns_Initializing |
2 | The network suite / job / task is being initialized. |
Running | ns_Running |
3 | The network suite / job / task is running. |
Stopping | ns_Stopping |
4 | The network suite / job / task is stopping. |
Synchronizing | ns_Synchronizing |
5 | The task is waiting for synchronization with other tasks by a particular synchronization point.
The network suite can also have this state when a task of a master project is waiting for synchronization with the tasks of slave projects. Jobs cannot have this state |
Waiting for CS | ns_WaitingForCriticalSection |
6 | The task is waiting for access to a particular critical section.
The network suite can also have this state when a task of a master project is requesting a critical section. Jobs cannot have this state |
Running in CS | ns_WorkingWithinCriticalSection |
7 | The task is working within a particular critical section and has exclusive access to it.
The network suite can also have this state when a task of a master project is working within a critical section. Jobs cannot have this state |
Verifying | ns_Verifying |
8 | The network suite / job / task is being verified.
Both master and slave projects are thoroughly checked. Unlike fast verification, this procedure invokes TestComplete on host machines. |
Fast verification | ns_FastVerifying |
9 | The network suite / job / task is being briefly verified.
This procedure checks the settings of the master project and whether the hosts and slave projects are available. TestComplete is not invoked on host machines. |
Slave Running | ns_SlaveRunning |
10 | This state is only displayed by the slave projects to indicate that they are involved in distributed testing. |
Waiting | ns_Waiting |
100 | The task is waiting for another hosts in order to start the task execution simultaneously. This state is displayed by a slave project that is ready to execute tests simultaneously, but is waiting for another slave project to be in such a state. This state is only applicable to tasks. |
See Also
Distributed Testing
Deprecated Features
Running the Network Suite, Jobs and Tasks
Network Suite Editor - Run State Page
State Property
State Property
State Property