However, due to the hard limit (60s) on the timeout during the
presubmit, the test is registered as a postsubmit test for now.
Also implement some helper methods and classes to make writing tests
easy.
Bug: 203483081
Test: atest MicrodroidTestApp
Change-Id: Ic07d776aff5f56421fc43a103a5b54b4a62b451f
This is a first step for making our tests to run on device.
MicrodroidTestApp now becomes a self-instrumenting test. The test
currently does nothing at the moment though.
Bug: 203483081
Test: atest MicrodroidTestApp
Change-Id: I675f622e9d014fb1bb358d4ab537dcd5377ba2ba
android.system.virtualmachine is added as the client-side API for the
controlling of virtual machines. This change doesn't add any new API.
It adds an empty library to the existing framework.
Bug: 183496040
Test: atest MicrodroidHostTestCases
Change-Id: I9c52dfaf7e33137e5e3d6c587b5cc3932f667025
A new requirement for 31
Bug: 190588547
Test: TARGET_BUILD_APPS=com.android.virt m; adb install <path>; adb
reboot
Change-Id: If03b6cb5eb64694cebaa56d037ead611d18d9b17
Change-Id: Ibe293169f39b74ec34b490dd216030c1d7221588
It's a test app (along with a native binary) that we will use to test
micdordoid. Right now, it doesn't have any test routine in it. For the
time being, the existing MicrodroidHostTestCases will use the apk to
check if zipfuse can correctly mount the file across the host Android
and microdroid. For this, the app right now is part of the virt APEX.
Later when we have app-facing Java APIs, the test app will be removed
from the virt APEX and installed separately (via adb install) and will
invoke the Java APIs and check the expected side effects.
Bug: 186377508
Test: m MicrodroidTestApp
Test: m com.android.virt
Change-Id: I929565f7fec1cd888ccc7a2b1c3021a2a85681ad
Jiyong Park