Add test coverage to test run logic.

Test coverage % is now ~63%, above 60% average rate.

Also in this CL:
* Cleaned up log directory after test run.
* Mobly test result and logs will be reported even if an exception was
thrown earlier.

Test: TF unit test.
Bug: 159641617
Change-Id: I59ccf20810b11c7e5d3a6aa5a893de6511b5e27d
2 files changed
tree: f4b8f72ce0e69cecb2e2175f12db31de6ad6abb0
  1. atest/
  2. clearcut_client/
  3. common/
  4. common_util/
  5. device_build_interfaces/
  6. global_configuration/
  7. invocation_interfaces/
  8. isolation/
  9. lite/
  10. proto/
  11. python-lib/
  12. remote/
  13. res/
  14. src/
  15. test_framework/
  16. test_result_interfaces/
  17. tests/
  18. util-apps/
  19. .classpath
  20. .gitignore
  21. .project
  22. Android.bp
  23. Android.mk
  24. atest_tradefed.sh
  25. CleanSpec.mk
  26. error_prone_rules.mk
  27. MANIFEST.mf
  28. OWNERS
  29. PREUPLOAD.cfg
  30. pylintrc
  31. README.md
  32. run_tf_cmd.sh
  33. script_help.sh
  34. TEST_MAPPING
  35. tradefed.sh
  36. tradefed_win.bat
README.md

Trade Federation (TF / Tradefed)

TF is a test harness used to drive Android automated testing. It runs on test hosts and monitors the connected devices, handling test scheduling & execution and device management.

Other test harnesses like Compatibility Test Suite (CTS) and Vendor Test Suite (VTS) use TF as a basis and extend it for their particular needs.

Building TF:

  • source build/envsetup.sh
  • tapas tradefed-all
  • make -j8

More information at: https://source.android.com/devices/tech/test_infra/tradefed/

See more details about Tradefed Architecture at: https://source.android.com/devices/tech/test_infra/tradefed/architecture

If you are a tests writer you should start looking in the test_framework/ component which contains everything needed to write a tests in Tradefed.