Group Exe test cases under a single test run

ExecutableBaseTest previously had a 1-to-1 wrapping of test runs to test
cases. There wasn't a hard reason for this and no real issues besides
when running something like the LTP test set you don't get a proper
incrementing test count. This became a bigger issue when trying to
leverage `onTestRunStart/End` for metric collector development. There
was no real difference in those calls and the finer resolution
`onTestStart/End` calls.

Test: ExecutableTargetTestTest, ExecutableHostTestTest
Bug: 257506360
Change-Id: I12b995d5669a60d3176ad94d9ebb8ae217fd0a0d
Signed-off-by: Joe Fradley <joefradley@google.com>
3 files changed
tree: 3d99fb9b463bfeb52732ecf589d59dd2ff54e7ac
  1. aoa_helper/
  2. atest_proto/
  3. clearcut_client/
  4. common_util/
  5. device_build_interfaces/
  6. external_dependencies/
  7. global_configuration/
  8. invocation_interfaces/
  9. isolation/
  10. javatests/
  11. lite/
  12. proto/
  13. reference_tests/
  14. remote/
  15. res/
  16. src/
  17. test_framework/
  18. test_observatory/
  19. test_result_interfaces/
  20. util_apps/
  21. .classpath
  22. .gitignore
  23. .project
  24. Android.bp
  25. Android.mk
  26. aosp_sha.sh
  27. atest_tradefed.sh
  28. CleanSpec.mk
  29. error_prone_rules.mk
  30. MANIFEST.mf
  31. OWNERS
  32. PREUPLOAD.cfg
  33. pylintrc
  34. README.md
  35. run_tf_cmd.sh
  36. script_help.sh
  37. TEST_MAPPING
  38. tradefed.sh
  39. 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

Getting Code Reviewed

1. Create your change in Gerrit
2. Add the reviewer named "Tradefed Codereview" (email: tradefed-codereview@tradefederation.google.com.iam.gserviceaccount.com)
3. Review the code review guidance at go/tf-guidelines and go/tradefed-code-reviews
4. GWSQ should add a couple of people from the team to review your code and give feedback.

More information

More information at: https://source.android.com/docs/core/tests/tradefed/

See more details about Tradefed Architecture at: https://source.android.com/docs/core/tests/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.