28.2 Starting and Connecting the Device

Note The Android application can either be tested on a real Android device or an emulator, an iOS application of a real iOS device or a simulator. Subsequently, the term "device" refers to any of the options.

Our first step is to examine the Setup node more closely:

Figure 28.3:  The Setup node

You will see two child nodes:

  1. Set variable – set the variable client to the connection name for the SUT, which will be needed for every action replayed to the application.
  2. Start device and connect – starts the corresponding Emulator (Android) or Simulator (iOS), or connects to a real device if a connection is not yet established, and opens the CarConfigurator app.
Figure 28.4:  The sequence to start the mobile device

In Start device and connect, the first entry is a Wait for client node to check whether the client is already running. Only if not, it will be started.

Starting the device is done in two steps:

  1. First, the Connect to Android device node tries to connect to to a real Android device or a running emulator. In case it fails QF-Test jumps to the Catch node where the Start Android emulator node starts the emulator if the given device is an emulator.
    Note: For iOS, the node Connect to iOS device is used to connect to a real device as well as to a simulator.
  2. Wait for mobile device – finalizes the connection to the Android device and for both technologies waits for the connection to be up and running.

These two steps are created automatically when using the Quickstart Wizard, which is explained in the next tutorial chapter ("Starting the Application").

Let's start the application:

During execution QF-Test marks the active step by use of an arrow pointer ->.

After the setup sequence is completed, the demo app "CarConfigurator" should appear on the Android device.

Figure 28.5:  The CarConfigurator Android demo