A GoogleTest (GTest, also sometimes called "native tests") for the platform typically accesses lower-level HALs or performs raw IPC against various system services. Because of this, the testing approach is usually tightly coupled with the service under test.
To integrate with continuous testing infrastructure, build your GTests using the GTest framework.
Examples
Here are some examples of GTest in the platform source:
Summary of steps
Follow the example GTest module setup.
To automatically include GTest dependencies, use the
BUILD_NATIVE_TESTbuild rule in your test module configuration.Write a test configuration, following the examples for simple and complex options.
Build the test module with
mmmfor incremental builds, ormmafor full builds:make hwui_unit_tests -jRun the test locally using Atest:
atest hwui_unit_testsYou can also add arguments to your GTests. The following are especially useful arguments:
native-test-flagspecifies additional flag values to pass to the GTest shell command.native-test-timeoutspecifies a test timeout value in microseconds.The following example code uses both of these arguments:
atest test-name -- --module-arg test-name:native-test-flag:"\"argument1 argument2\"" \ --module-arg test-name:native-test-timeout:60000
Run the test with the Trade Federation test harness:
make tradefed-all -j tradefed.sh run template/local_min --template:map test=hwui_unit_testsManually install and run:
Push the generated test binary onto your device:
adb push ${OUT}/data/nativetest/hwui_unit_tests/hwui_unit_tests \ /data/nativetest/hwui_unit_tests/hwui_unit_testsLaunch GTest and execute the test by invoking the test binary on the device:
adb shell /data/nativetest/hwui_unit_tests/hwui_unit_testsFor more information about customizing test execution, add the
--helpparameter to your test binary. For more information on parameters, refer to the GTest advanced guide.