The users moved over to GetOutDir, and this shouldn't be parsing
report_config, so remove it.
Test: cs/GetHostOsArch
Change-Id: I9c045071af7f210b4ec19f158016ff53978a8a6c
This takes the --test-class and --test-method options and builds a
--gtest_filter value to use when invoking native tests.
How it works:
ARGS to runtest ARG to GTEST
--test-class= --test-method= <none>
--test-class=Foo --test-method= --gtest_filter=Foo.*
--test-class= --test-method=Bar --gtest_filter=*.Bar
--test-class=Foo --test-method=Bar --gtest_filter=Foo.Bar
Advanced:
-m *Iptables* runs all test methods containing 'Iptables' in any class.
-c *ControllerTest runs all tests in any class ending with 'ControllerTest'.
Note that the '.' and '*' characters above are not shell globs. The '*'
are wildcards, and the '.' are literals.
Test: runtest -x system/netd/server/netd_unit_test.cpp -m '*Iptables*'
Test: runtest -x system/netd/server/netd_unit_test.cpp -c BandwidthControllerTest
Test: runtest -x system/netd/server/netd_unit_test.cpp -c BandwidthControllerTest -m '*Iptables*'
Change-Id: I967296da1bdcbc404f5ab91d24f9714eec7b475b
Some tests were moved from frameworks/base 7 years ago (ag/54455),
but the rule was never added so they couldn't have been run with
testrunner.
Test: testClass can be run with "runtest -c testClass android-common-ex"
Bug: 62161211
Change-Id: Ie70f0fc32ceec59c3d89be75415adff34c1402ed
This was installing all modules defined in Soong, since we always load
the Soong-generated Makefile for mm/mmm. So use MODULES-IN-* instead of
all_modules.
Also switch to the new GET-INSTALL-PATH-IN-* arguments.
Bug: 30191725
Change-Id: I8a660e24c9933f3f77eb23efd71f8e374a248576
( cherry-pick of 00d6fa79f7 )
Specifying a runner allows developers to run commands like:
`runtest frameworks-services`
without getting a message like:
"Could not find instrumentation
com.android.frameworks.servicestests/android.test.InstrumentationTestRunner
on device."
Bug: 28833951
Change-Id: I76fb58a8fa16db503c8e98eb5a09c481d41e0a76
Test: Described above
Specifying a runner allows developers to run commands like:
`runtest frameworks-services`
without getting a message like:
"Could not find instrumentation
com.android.frameworks.servicestests/android.test.InstrumentationTestRunner
on device."
Bug: 28833951
Change-Id: I76fb58a8fa16db503c8e98eb5a09c481d41e0a76
Test: Described above
--install-filter parameter is a regular expression that will be used
to match the compiled apks to determine if it needs to be installed.
This is very helpful when there are many apks in a test directory,
but you only care about one during development.
e.g. fw/base/core/tests/coretests
Change-Id: I6a6a04640e549be4d90c9c659e557e7870af6771
Currently runtest script installs and then runs test apks with default
"adb install" and "adb shell am instrument" behavior. They are actually
different, "adb install" uses USER_ALL, "am instrument" uses
USER_CURRENT. This cl introduces a way to specify exactly which user a
test should run with in a multiple user environment. This also provides
a work around for b/22976637 for now.
Bug: 19913735
Bug: 22976637
Change-Id: I65e2b2c79768734a8bc9261f8c4693c9f89016b1
