Bug: 151896491
Test: presubmit check
Exempt-From-Owner-Approval: This CL renames suite name vts-core to vts.
It won't change test logic or behavior.
Change-Id: I79cddf5e4a65486b8f1286ea430360479ad2b93d
VTS provides rootable environment for ApkVerityTest to run.
ApkVerityTest needs to write block device to verify the failure case of
fs-verity.
Test: see ApkVerityTests and block_device_writer in `unzip -l
out/host/linux-x86/vts-core/android-vts-core.zip`
Bug: 150641206
Change-Id: Idc71907a28f68fc873c5cac940aa706e0b79843e
By keeping block_device_writer_module in target_required, it avoids
build error of "missing variant: os:linux_glibc, arch:common", while
the test still run on forrest.
Test: forrest
Test: lunch flame-eng; atest ApkVerityTest
Test: lunch aosp_x86_64-eng; m ApkVerityTest
Bug: 112039386
Change-Id: I9cfa0928941b008e23c2a32bb47dae5369bd3201
There are two categories of tests:
1. Package installation with .fsv_sig
* .apk, .dm, including the split ones should all or none be installed
with their corresponding .fsv_sig files
2. End-to-end fs-verity test of on-access verification
* When fs-verity is enabled to a file, if the on-disk content is
changed, the read should fail.
See class comment in ApkVerityTest.java for the test details.
Brief directory layout overview:
* src/
- Actual test
* ApkVerityTestApp/
- Dummy app for testing, including a split
* testdata/
- Some artifacts, signing key and fs-verity signatures
* block_device_writer/
- Helper binary for write a file directly on disk
Test: atest
Bug: 112039386
Change-Id: I3b8229037db682f36fda9d5cafd14caf6b39501d
