Test Runner is the execution unit of the invocation flow. This is where tests actually run.
Test Runners are defined via the
which provides a simple
run method to implement that will be called when the
tests is to run.
This allows the simplest definition of a test run to occur. But in practice, test writers will need more information to properly write their tests, typically build and device information. This is where the following interfaces come handy.
These two interfaces are the most widely used today, as they represent the basic needs of most tests.
allows the test to get the
IBuildInfoobject created at the build provider step containing all the information and artifacts related to the test setup.
allows TF to receive the
ITestDeviceobject that represents the device under test and provides an API to interact with it.
There are additional interfaces that allow more complex interaction between the test harness and the test runner:
- ITestFilterReceiver, which allows the test to receive a set of filters for running certain tests only. This is useful in running a subset of the tests.
- ITestCollector, which allows a test runner to only dry-run the tests instead of actually executing them. This is useful in collecting the list of all test cases.
Existing test runners
A variety of test runners already exists, some for major test types:
- AndroidJUnitTest / InstrumentationTest (associated with AJUR on the device side)
- GTest (device and host side) with googletest library
- Host-driven tests (Java tests that execute on the host and call the device from there)
- Pure Java unit tests (our runner does both)
- Python tests
- Google Benchmark tests with benchmark library
A large number of custom test runners exist besides the above; they serve specialized purposes for some functional testing, for example Boot Test.
Writing new a test runner
More guidance of writing a new test runner is available in the writing tests section.