It might seem like a lot of work to get to this point, but consider what you have accomplished and what can be accomplished. You have:
Modeled dynamic, distributed component interaction
Created virtual testers that could, simply by specifying various IP addresses, execute on multiple machines
Enabled load testing
Provided a means for implementing scenario-based testing
Each step you performed, in reality, has hidden an enormous amount of complexity.
In this section, you will run the test.
To execute the test:
Run the System Testing agent software - that is, run the software that supports virtual tester execution. The agent executable is called atsagtd and it can be executed in one of two ways:
On Windows - In the Start menu, select Programs > HCL Software > HCL OneTest Embedded > Tools->HCL OneTest Embedded System Testing Agent (which is simply a link to the file atsagtd.exe, executable from the command line with a single argument - the port number to be used, 10000 in this case). Minimize the command window that appears.
On Linux - This agent is already launched if you have followed the System Testing Agent installation instructions in the HCL OneTest Embedded User Guide, in the System Testing Overview chapter.
When test execution has completed, a post-execution trace of events will be created; this trace is used later in the tutorial. However, if you wish to monitor execution via an on-the-fly trace as well, follow the next five steps. Otherwise, skip to Step 7.
Right-click the MobilePhoneVT system testing node on the Project Browser tab and select Settings
Expand the System Testing node on the left-hand side of the Configuration Settings window, select the Advanced options node and then select Yes in the dropdown list associated with the property On-the-fly tracing.
From the Window menu, select Close All.
Now run the test.
Left-click the MobilePhoneVT system testing node and press the Build button. (If you are asked to rebuild the nodes, click the Yes button.) The test harness is now built, deployed, and executed.
If you opted to create an on-the-fly trace: The Runtime Trace viewer will appear. The test has finished executing when the right-hand phone1_0 lifeline in the viewer is stamped at its base by a black X:
If you opted to not create an on-the-fly trace: Execution has completed when the green execution light in the lower-right of the OneTest Embedded GUI stops flashing ()
From the File menu, select Save Project.
On Windows only - close the System Testing Agent.
The on-the-fly runtime tracing diagram shows interactions, as they happened, between the software-under-test (SUT) - that is, the UMTS base station - and the single virtual tester you had created for the system test. This virtual tester is named phone1_0. Such an on-the-fly diagram is useful for monitoring test execution; however, this diagram is not crucial to the extent that the information within it has also been captured for post-execution analysis in a separate runtime tracing diagram.
In the next exercise, you will look at this runtime tracing diagram and then study the system test report.