Stop using 'adb sync' in runtest. It was unreliable even when working
with full platform builds, and doesn't work at all for unbundled apps.
Instead, use output from build command to find produced artifacts and
use 'adb install' where possible.
However, note that this approach won't sync previously built artifacts
to device.
Also adjust to build system support for code coverage. Its no longer
required to build libcore to get code coverage.
Change-Id: I9c5d37897c9570d2d29db3ec82f5c53e60a8f485
InstrumentationTestRunner can enumerate the test cases to run without a
special TestRunner in KeyStoreTests.
Change-Id: I9e849d035d78b51ca9a73c52012dab448fc4a7ee
Update "runtest" to find the frameworks-telephony test cases in
frameworks/opt/telephony instead of frameworks/base/telephony.
Change-Id: I90597ee65b56df5fbe12a1a6730f6ac409443fe8
- No need to include cts/CtsBuild.mk, because that is included by the
core build system.
- Include the tradefed-prebuilt.jar on the classpath when running
host side tests.
- Update some of test_defs that have changed. Remove suites that
have been deleted.
Change-Id: Ie2845db7f209ad4ccb881d2ad47b9415c9f518a4
The CTS packages use CTS-specific Makefiles rules like
BUILD_CTS_PACKAGE instead of BUILD_PACKAGE. Update runtest
to include CtsBuild.mk which defines all of these.
Change-Id: I6ea6c77b4f2ab113126319141e5120e016055c9d
We re-organized the code to live in one of the existing packages and
therefore we no longer need the tests to be run on their own.
Change-Id: I55e6e58628d384218adc6c116f790b540709ec3c
A recent change to runtest resulted in absolute paths incorrectly
being used for a tests build path. This broke the special logic
for frameworks/base tests, since it assumed relative build paths.
Change build paths back to relative paths.
Bug 5105885
Change-Id: I83a26be25294d501cca73eb1b88a7364131b2caf
This is a rough initial version. It makes several assumptions:
- assumes each test source file is built into module with name equal
to basename of source file
- assumes tests get installed into /data/nativetest
However, given those assumptions, both:
$ runtest --path <path to directory containing gtest source> and
$ runtest --path <path to single source file>
should work.
Coming soon: gtest host support
Bugs 4563370, 4584339
Change-Id: Ia42aeed7f9ee6402b0ceb7b5ccaaa66ac636fe49
Previously runtest would fail hard if development/test_runner/test_defs.xml
file was not present, even if it wasn't needed (ie running in --path mode).
This commit skips test_defs parsing if --path is specified, and only parses
development/test_runner/test_defs.xml if its present.
Bug 4556556
Change-Id: Ief2dbbdab5c7e82e5db64414392d6e2a564e815d
Dependent on change Ib6d9a81f3bfa68cbd25d2189f6e6690bc3d8e428
(which adds the necessary test size annotations).
Bug: 1847330
Change-Id: I206385e5da7f2c496043568cba848304b52a6475
