Don't include configs with same name, diff content

We may have configs with same name, but with different content. for
example, if they are host and device variants of the same test config.
prioritize-host-config flag is used to decide which config to select if
multiple configs exist, by reordering the test folders mainly. returning
duplicates breaks this logic. So, adding this logic inside a flag only.
this is still needed for validating all configs, including the
duplicates.

Bug: 286559640
Test: Presubmit
Change-Id: I97d06e2558fc0783dc17c1aea4980e72f2ee9434
2 files changed
tree: 3f8e01cf634376961e8e73e3477030ae38a1e394
  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. MULTIUSER_OWNERS
  32. OWNERS
  33. PREUPLOAD.cfg
  34. pylintrc
  35. README.md
  36. run_tf_cmd.sh
  37. script_help.sh
  38. TEST_MAPPING
  39. tradefed.sh
  40. 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.