Testing

:::note[TODO]

This article is a work in progress.

:::

CTS Testing

TBD

VTS Testing

Prerequisites

• You have run ./build.sh with the --with-vts option enabled

• Ensure the resulting userdebug variant build is flashed on to at least one device

• Start up these devices and complete the setup wizard as follows;

  • select language, time format,
  • connect to a wifi network,
  • skip the Aphy account signup or signin,
  • turn the volume down or off.

• Connect the devices USB-C port to the system running the VTS testing framework.

Executing Tests

Simply put, run ./vts-test.sh.

This script will;

• run source build/envsetup.sh from ${APHY_ROOT}/vendor/,

• run lunch full_<model>-userdebug, where <model> is, for example, k6877v1_64_k419,

• run make vts,

• unzip the resulting android-vts.zip to ${APHY_ROOT}/tmp/android-vts/

• optionally, adjust JAVA_HOME and PATH to fit your setup:

  export JAVA_HOME=/usr/lib/jvm/java-1.8.0/
  export PATH=/usr/lib/jvm/java-1.8.0/bin/:$PATH
  

• preferrably in the same shell, run tmp/android-vts/tools/vts-tradefed,

• execute the run vts --shard-count <NUM> command in the vts-tradefed shell, where <NUM> is the number of devices with unique serial numbers attached to the workstation (see the standard output of vts-tradefed for devices successfully detected).

:::note[Outputs are independent from tmp/]

If vts-tradefed has been executed in the same shell, the results live in ${APHY_ROOT}/userdebug/out/host/linux-x86/vts/android-vts/results/. If launched from a separate shell, results may live in ${APHY_ROOT}/tmp/android-vts/results/.

:::

Aphyium Testing

TBD