 |
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. |
About Network Suite Verification
Before TestComplete runs a distributed test, it verifies the network suite. The verification procedure includes numerous checks and if any of them fails, TestComplete informs you about it so that you can fix the problem quickly.
The verification procedure confirms the following:
-
On the master computer:
-
The user account under which TestComplete is running has permissions to share the folder specified by the Shared path property of the master project.
-
The remote computers defined in the master project’s Hosts collection have a network name or IP address specified in the Address property.
-
The remote computers defined in the master project’s Hosts collection are available on the network.
-
The login information (user name, password and domain) for each remote computer is specified in the Hosts editor or in the Network Suite Editor - Properties Page.
-
-
On a remote computer:
The following checkups are performed only on remote computers available on the network. -
If no user is logged in to the computer, TestComplete ensures that the provided user account can successfully log in.
If there is an open user session, TestComplete ensures that the provided user account is the same as the logged in user. (This way TestComplete will be able to connect to that session from the master computer).
Note: Server editions of the Windows operating system support multiple concurrent user sessions. If several user sessions are open on a remote host, the network suite will close all those sessions and open a new session for the needed user. -
TestComplete 15 (or TestExecute 15) is installed.
-
TestComplete 15 Service is registered and can start (if it is not already running).
-
TestComplete (TestExecute) can start (if it is not already running).
-
The slave project or project suite specified by the task’s Project file name property exists and is available to the logged on user. (A limited user account may have no permissions to access the project file.)
-
TestComplete (TestExecute) can open the needed project on the remote host.
-
The slave project contains the NetworkSuite project item.
-
The slave project contains the test specified by the task’s Test property.
Note: An empty Test value corresponds to the entire slave project suite.
-
Verifying a Network Suite From the TestComplete UI
To ensure that the network suite is configured correctly without running it, open your master project and verify the network suite or its individual hosts, tasks and jobs.
To verify a remote host
-
In the Project Explorer, expand the project’s NetworkSuite | Hosts collection.
-
Right-click the host and then click
Verify.
-- or --
-
Double-click the NetworkSuite | Hosts item in the Project Explorer. The Hosts editor opens.
-
Select the desired host in the list and click the
Verify button on the editor’s toolbar.
To verify a task
-
In the Project Explorer, expand the project’s NetworkSuite | Jobs | JobName collection, where JobName is the name of the job that contains the task.
-
Right-click the job and then click
Verify.
-- or --
-
Double-click the NetworkSuite | Jobs item in the Project Explorer. The Jobs editor opens.
-
Right-click the desired job in the list and then click
Verify.
To verify a job
-
In the Project Explorer, expand the project’s NetworkSuite | Jobs collection.
-
Right-click the job and then click
Verify.
-- or --
-
Double-click the NetworkSuite | Jobs item in the Project Explorer. The Jobs editor opens.
-
Right-click the desired job in the list and then click
Verify.
TestComplete will verify all the tasks in the job.
To verify the entire network suite
-
Right-click the NetworkSuite project item in the Project Explorer panel and then click
Verify.
TestComplete will verify all the hosts, jobs and tasks in the network suite.
Verifying a Network Suite From Tests
You can add network suite verification commands to your keyword and script tests:
-
Host.Verify- verifies a specific remote host, -
Task.Verify- verifies a specific task, -
Job.Verify- verifies all the tasks in a specific job, -
NetworkSuite.Verify- verifies the entire network suite, that is, all the hosts and tasks.
To call these methods from a keyword test, use the Call Object Method or Run Code Snippet operation. For more information, see Calling Object Methods.
If a network suite, job or task is currently running, the Verify method will wait until it finishes running and becomes idle. For example, take a look at the script below that runs two tasks:
VBScript
NetworkSuite.Jobs(0).Tasks.ItemsByName("Task1").Run(False)
NetworkSuite.Jobs(0).Tasks.ItemsByName("Task2").Verify ' This line is executed once Task1 is over
NetworkSuite.Jobs(0).Tasks.ItemsByName("Task2").Run
The Task1.Run(False) method commands TestComplete not to wait for Task1 to finish before continuing running the test, however, Task2 will run only after Task1 is over. This happens because the Task2.Verify method waits for Task1 to finish before verifying Task2.
See Also
Creating and Running Distributed Tests
Distributed Testing - Requirements
Distributed Testing
Projects Participating in Distributed Testing
Running the Network Suite, Jobs and Tasks