Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Current »

UPDATE 25 NOV 2024

You can use an android emulator to help you develop your GDSL tests. It is useful if you do not have a real device or if you want to test on a device with the same resolution as a device on the Test Bench. Do not use emulator if you want measures, the metrics (energy, data …) are not available.

1 - Change the job.yml file

job:
  extras:
    config-skipsetupphone: true

To be able to run an application with the applicationStart gdsl function, there are 2 choices :

  • Install the app manually through the Play Store application or with adb or other mechanism

  • In the job.yml file, add an apps field with a list of application to install at the beginning of the test and to uninstall at the end. (package could be a package name for playstore or a local path to an apk or a public url to an apk). Example :

job:
   apps: 
    - com.myapp

2 - Change the config.yml file

target:
  connection: usb
  serial: xxxx

The target.serial field corresponds to the emulator id. You can find it by running “adb devices”.

3 - Run the testrunner

  • Launch an android emulator

    • Option 1: open the Device Manager window of Android Studio and click on the triangle

    • Option 2: start an emulator from the command line (part 2.5)

  • Run the testrunner

    • On Linux and macOS: ./testrunner -jobFile job.yml -config config.yml

    • On Windows: testrunner -jobFile job.yml -config config.yml

On macOS with M1 chip, you may need to install Rosetta first:

/usr/sbin/softwareupdate --install-rosetta --agree-to-license

  • No labels