| commit | b0ea4e3cd4066a245cd1cd7f9015e9aa4a281e72 | [log] [tgz] |
|---|---|---|
| author | Joseph Murphy <murj@google.com> | Mon Jan 06 15:58:16 2020 -0800 |
| committer | Joseph Murphy <murj@google.com> | Mon Jan 13 13:53:47 2020 -0800 |
| tree | 5abf0a4fb4539b7b4e319e4044896c89efb21641 | |
| parent | 0317d386021c6a50dce34bf2be6a8542119e6d8f [diff] |
Adds a variety of refinements to isolation runner. When initially trying to run some of the robolectric tests under this new runner, there arose some unforeseen issues (like dependencies including things in the java.lang package) that for now are mitigated by the runner. Additionally, the change to using RunUtil inadvertantly disabled output streaming from the subprocess, which this CL fixes. Lastly for the major changes, this changes the qualification of what counts as "the correct annotations" which excludes classes which specify the "RunWith" annotation, but use a runner that does not subclass the JUnit4 runner. Edit #1: I moved the fakeExecution out of HostUtils into a proper class that extends the JUnit Runner API. This makes the flow when dry running a test quite a bit more similar to the flow when running for real. Bug: b/130198687 Test: incomplete, but no regressions in existing Change-Id: I4a6fda942e47978506a6ddc82c5f8a03dc04b690
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:
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.