tree: e55c2c2df28b674349e89be4cb1acd95654d8026 [path history] [tgz]
  1. vm/
  2. Android.bp
  3. AndroidTest.xml
  4. README.md
  5. trusty-test_vm-config-arm64.json
  6. trusty-test_vm-config-x86_64.json
  7. trusty-ut-ctrl.sh
  8. trusty-vm-launcher.sh
  9. trusty-wait-ready.sh
guest/trusty/test_vm/README.md

test_vm

The Trusty test_vm ought to include the test TAs for the Trusted HALs, defined under hardware/interfaces/security/see:

  • AuthMgr
  • Secure Storage
  • HWCrypto
  • HDCP

The Trusty test_vm also includes the VINTF test which allows to check the vendor support of the Trusted HALs (version and API hash), against the expected compatibility matrix for a given Android Dessert Release.

instructions

`atest -s VtsSeeHalTargetTest

test_vm console

The test_vm console can be retrieved from /data/local/tmp/trusty_test_vm/logs/console.log. The script trusty-vm-laucher.sh uses /apex/com.android.virt/bin/vm run with the option --console to store the console log.

This log can be consulted when the tests are running and will be uploaded by the Tradefed FilePullerLogCollector runner (see AndroidTest.xml).