Deploying virtual testers

Each virtual tester driver can be used to create one or more virtual testers. In addition, if the driver supports more than one INSTANCE block, then each specific INSTANCE block needs to be assigned a virtual tester. For this tutorial, you will just be running a test that consists of a single virtual tester.

To set up the Deployment Configuration:

  1. We are still in the System Testing wizard. On the Deployment Configuration (6/7) page, click the Add button to create a virtual tester.

The Virtual Tester Driver column is used to select the driver, the INSTANCE column is used to select the INSTANCE, and the Network Node column is used to specify the machine to which the virtual tester(s) will be deployed. Since only one virtual tester is required for the tutorial, the column Number of Occurrences can remain equal to 1.

  1. Select phone1 in the Instance column and ensure the Network Node is 127.0.0.1, which is the local host. You can use either a host name or an IP address.

  1. Click the Next button.

  2. Review the settings on the Test Generation Summary window if you wish, then click the Finish button.

You're system test node should appear as follows in the Project Browser:

 

Note that if, at any point, you feel the need to modify the deployment configuration, you can right-click the test script node (in this tutorial that would be the MobilePhoneVT.pts node) and select the Virtual Tester Driver Configuration option.

One step remains. Recall that you will be using UMTS base station files to implement the messaging API. During the System Testing Wizard you selected the two header files that contain the API specification. What you must do now is reference the source files that implement the messaging API. This could not be done in the wizard because there was no messaging-API library to import. The source files for the messaging API need to be compiled along with the test script and thus must be added directly.

  1. Right-click the virtual tester driver node driver1 on the Tests tab and select Add Child->Source Files

  2. Browse to the UMTS base station source files located within HCL OneTest Embedded installation folder, in the folder \examples\BaseStation_C\src, and open all of the C language files:

  1. From the File menu, select Save Project.

There is no need to instrument the three C language files used to implement the messaging API, but rather than altering the entire TDP configuration using the Build dropdown menu, you are simply ensuring these three particular files won't be instrumented.

You are now ready to simulate the mobile phone and thus drive the UMTS base station, ensuring the base station responds to signals in a proper and timely fashion.