75b84e4cb4ed4ea54566a61b183c5a01837befa7
frameworks-base-testutils is unused in tethering integration tests, so the dependency can be removed. That test library also contains test classes, so removing the dependency allows tethering tests to stop running the associated tests. Also add jarjar rules to the unit tests to zap (remove) the test classes from the output APK. Ideally the unit tests should stop depending on that library too (TestableLooper can be used instead of TestLooper), or the frameworks-base-testutils library should stop including test classes. Bug: 167968946 Test: m CtsTetheringTest TetheringTests Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1433924 Merged-In: I3f1d7019f1a12647b78630a412df3adf03e9e95a Change-Id: Id189676b7447c6cb0f8d9b216c42a34c6513ba61
Description
android_packages_modules_Connectivity
Languages
Java
81.4%
Kotlin
7.7%
AIDL
4.5%
C++
4.5%
C
1.7%
Other
0.1%