| commit | 4d7183ec470f63ad6d000a32f7c3bec7470c0369 | [log] [tgz] |
|---|---|---|
| author | Roland Levillain <rpl@google.com> | Tue Sep 08 13:24:16 2020 +0100 |
| committer | Roland Levillain <rpl@google.com> | Tue Sep 08 19:44:24 2020 +0100 |
| tree | 444011a47d35f8064ac86b756b2b3dd4f5862d8d | |
| parent | 18a5c18513cc9af5e67fed85ba1cc05ce7782564 [diff] |
Use new file names of ART run-test expected-output files in `ArtRunTest`.
Expected output files now have a unique name, in order to support
TradeFed test suites. (Previously these files were all named
`expected.txt` and would telescope each other when added to the set
of "flattened" tests artifacts of a test suite package.)
This partially reverts commit 9f052906640b4b1b4a05484896adeb09c230e4e4.
Test: m tradefed tradefed-tests
Test: tools/tradefederation/core/tests/run_tradefed_tests.sh \
--class com.android.tradefed.testtype.ArtRunTestTest
Test: atest art-run-test-001-HelloWorld
Bug: 147812905
Change-Id: Ie90eed7fe66cd5e207180f39dd3b4f1e8a9956a4
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/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.