commit | 9b75af8d97e649ca4bd88876bb63f4c893b99839 | [log] [tgz] |
---|---|---|
author | Ben Murdoch <benm@google.com> | Tue Nov 01 17:49:51 2022 +0000 |
committer | Treehugger Robot <treehugger-gerrit@google.com> | Mon Nov 07 17:14:08 2022 +0000 |
tree | 667315e7e0bd1bfe7894f915dfdc43ea107b56de | |
parent | 3d989b02c19071e1a095246331e1fc969de8771f [diff] |
On device GTest working directory Before executing an on device GTest, change working directory to that of the gtest binary. This makes sure that tests that reference data using a relative file path will be able to find it. Bug: 256658467 Test: TreeHugger Change-Id: I3f0c0dc0bc63aa4726baaeeac53b8016f4209d31
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.