Adding FirmwareBootHeaderVerification

Bug: 149182947
Test: atest FirmwareBootHeaderVerification

Change-Id: I53a609b3fcd0a28e0fe93b0c5b8bfa96605e2225
Merged-In: I53a609b3fcd0a28e0fe93b0c5b8bfa96605e2225
4 files changed
tree: 499d9bcd61484bf0ca50aec9c0fb450bde1dbf70
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. prebuilts/
  8. proto/
  9. runners/
  10. script/
  11. specification/
  12. testcases/
  13. tools/
  14. utils/
  15. .clang-format
  16. .gitignore
  17. __init__.py
  18. OWNERS
  19. PREUPLOAD.cfg
  20. README.md
  21. setup.py
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:

  • the Android system (e.g., Core HALs and libraries) and
  • low-level system software (e.g., kernel, module, and firmware).

VTS has mainly two types of test suites:

  • automated (e.g., record-and-replay and fuzzing) and
  • structural (e.g., gTest and host-driven python) testing.

While the VTS framework and test cases are designed for userdebug or eng build devices, some test cases can be run on user build devices using its app namely, VTS Agent App.

Table of Contents

  1. VTS User Manual
  2. Where to find VTS test cases
  3. VTS Test Developer Manual (Codelab)