Android projects used by Tast tests

This directory contains Android projects that are used by Tast tests. They are built at the same time the ChromeOS test image is built, and not updated by tast run command automatically.

Using an APK under the directory in Tast

Take ArcGamepadTest.apk for example.

p := s.PreValue().(arc.PreData)
a := p.ARC

if err := a.Install(ctx, arc.APKPath("ArcGamepadTest.apk")); err != nil {
  s.Fatal("Failed to install the APK: ", err)
}

Updating APKs on the device

# one time setup
setup_board --board=${BOARD}

cros_workon --board=${BOARD} start tast-local-apks-cros
emerge-${BOARD} tast-local-apks-cros
cros deploy --root=/usr/local ${DUT_IP} tast-local-apks-cros

Then you can run normal tast run command.

Finding the built APKs

In the chroot they can be found under /build/$BOARD/usr/libexec/tast/apks/local/cros

On the DUT they can be found under /usr/local/libexec/tast/apks/local/cros/

Code Styles

Please follow AOSP Java style unless there is a specific reason not to.

Currently, we have a limitation that prevents us from using any external library for building apks (b/217501318). This includes the androidx support library. All code must be written using the standard Android SDK only. If androidx or some other dependencies are needed, it’s still possible to place your source code in the ARC++ internal repository and use the prebuilt apk as external data (example). However, this is not recommended from a maintenance perspective.

About OWNERS

Tast reviewers (tast-owners@google.com) are experts on Go language and Tast tests, but not Java and Android. Thus, we have additional OWNERS for this directory to review Android and Java code.