Having performed the runtime analysis exercises, you have seen how a mobile phone simulator can be used to interact with the UMTS base station. The implication then is that signals were being traded between the two.
If this is the case - if, in fact, signals are passed between the mobile phone simulator and the UMTS base station - would it not be useful to "fake" the simulator with a test that can send signals to the base station and then analyze the content and timing of the signals that are returned?
You will be doing just that. You will be simulating the simulator, creating a test that can interact with the base station in a well-defined way and then test the returned signals. Put another way, you will be automating the manual interaction you performed in the Runtime Analysis portion of this tutorial.
This test is coded with a system testing test script API.
In order to build this system testing test script - that is, in order to create virtual testers - the test script code must have access to the C language messaging API used by the system under test. Without a messaging API, it would not be possible to define the signals sent from the virtual tester to the system under test, nor would it be possible to analyze the returned signals. The messaging API might be accessible in a preexisting library, accessible in source code used to build the system under test, or inaccessible (thereby necessitating manual creation of a referenceable messaging API file). In this tutorial, you will be reusing some of the UMTS base station source files; these files define the messaging API used to communicate with mobile phones.
In addition to having access to the messaging API, you must also define an adaptation layer. The adaptation layer describes how the API is to be used; in other words, how are messages sent and received.
Finally, your test script will need to describe the action of a virtual tester - indicated in a system testing test script with the reserved keyword INSTANCE. This is the part of the test script that specifies what signals are sent to the target, what signals are expected, and any timing requirements.
To summarize: When building a System Testing test, you are responsible for:
creating or providing access to the C language messaging API
coding the adaptation layer
coding the INSTANCE blocks describing the simulated behavior and tests
You will not be responsible for creating any of these above items in the Tutorial - the files are provided for you - but their content will be reviewed.
You need to install the System Testing agent software, a daemon that must be running on the host to act as an interface between virtual testers and the machine running Test RealTime.
For Windows users, this daemon has already been installed.