commit | 3198546039545e093e822dc6d077bc3404171f2f | [log] [tgz] |
---|---|---|
author | bkchoi <bkchoi@google.com> | Fri May 17 15:10:07 2024 -0700 |
committer | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | Mon May 20 19:34:10 2024 +0000 |
tree | 0c7c3f8a96825b4b61e4b984cfc430698f7ed0d5 | |
parent | 196e7ef353e4b85472ea49abe8f59d32274e18d7 [diff] |
Add a utility method to extract RUN_TESTS_AS_USER. Add a new getTargetUserId() method to UserHelper, so it can be used to extract the userId that the test runs as, set in the TestInformation. Bug: 336880935 Test: m -j tradefed-all Test: atest android.media.player.cts.MediaPlayerSurfaceTest Change-Id: Icfd010342a069ca80232032567356e481f1abfe3
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.
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 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.