d137c872cdc5e157c0ff65076689f7c4552a9013 |
|
23-Feb-2018 |
Anton Hansson <hansson@google.com> |
frameworks/base: Set LOCAL_SDK_VERSION where possible. This change sets LOCAL_SDK_VERSION for all packages where this is possible without breaking the build, and LOCAL_PRIVATE_PLATFORM_APIS := true otherwise. Setting one of these two will be made required soon, and this is a change in preparation for that. Not setting LOCAL_SDK_VERSION makes the app implicitly depend on the bootclasspath, which is often not required. This change effectively makes depending on private apis opt-in rather than opt-out. Test: make relevant packages Bug: 73535841 Exempt-From-Owner-Approval: Global cleanup Change-Id: I26458e41ecb84de91ac9a356a5d4bafb44f463c1
/frameworks/base/wifi/tests/Android.mk
|
2710ca1e9d5ed8b2e755a9b948be8113ebb82023 |
|
05-Dec-2017 |
Paul Duffin <paulduffin@google.com> |
Flatten dependency hierarchy of legacy-android-test Previous changes statically included legacy-android-test in preparation for removing android.test.* and junit.* classes from the android.jar. Unfortunately, that lead to duplicate classes between APKs and the bootclasspath which caused build problems (Proguard) and also runtime problems (when targeting and running on older releases). Switching from statically including the classes to using the runtime libraries cannot be done in one step because legacy-android-test is statically included in libraries which are used in many APKs and so removing it from those libraries requires that all APKs be updated at once. Doing that atomically across dozens of projects is not practical. This change modifies APKS that statically include the legacy-android-test library indirectly. * If the APK manifest uses the android.test.runner library then the APK is modified to stop statically including legacy-android-test and instead build against android.test.base/mock/runner libraries instead. * Otherwise, the APK statically includes legacy-android-test. Also, any libraries that statically include are modified to stop statically including it and if it has source dependencies on the classes is changed to build against the android.test.base/mock/runner libraries. The following change descriptions were generated automatically and so may be a little repetitive. They are provided to give the reviewer enough information to check the comments match what has actually been changed and check the reasoning behind the changes. * cmds/uiautomator/instrumentation/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because uiautomator-instrumentation is not a package so does not need to statically include the classes * cmds/uiautomator/library/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because uiautomator.core has a source dependency on its classes Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because uiautomator.core is not a package so does not need to statically include the classes * core/tests/BroadcastRadioTests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BroadcastRadioTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that BroadcastRadioTests specifies in its manifest. * core/tests/coretests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because FrameworksCoreTests's source depends on their classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksCoreTests specifies in its manifest. * core/tests/featureflagtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksCoreFeatureFlagTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksCoreFeatureFlagTests specifies in its manifest. * core/tests/systemproperties/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksCoreSystemPropertiesTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksCoreSystemPropertiesTests specifies in its manifest. * core/tests/utillib/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because frameworks-core-util-lib is not a package so does not need to statically include the classes Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because frameworks-core-util-lib has a source dependency on its classes * core/tests/utiltests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because FrameworksUtilTests's source depends on their classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksUtilTests specifies in its manifest. * location/tests/locationtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksLocationTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksLocationTests specifies in its manifest. * lowpan/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksLowpanApiTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksLowpanApiTests specifies in its manifest. * packages/Osu2/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because OsuTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that OsuTests specifies in its manifest. * packages/SettingsProvider/test/Android.mk Replaced 'legacy-android-test' with 'android.test.base' in LOCAL_JAVA_LIBRARIES because SettingsProviderTest's source depends on its classes. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that SettingsProviderTest specifies in its manifest. * services/tests/notification/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksNotificationTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksNotificationTests specifies in its manifest. * services/tests/servicestests/Android.mk Replaced 'legacy-android-test' with 'android.test.base' and 'android.test.runner' in LOCAL_JAVA_LIBRARIES because FrameworksServicesTests's source depends on their classes. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksServicesTests specifies in its manifest. * services/tests/shortcutmanagerutils/Android.mk Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because ShortcutManagerTestUtils has a source dependency on its classes * tests/AppLaunch/Android.mk Replaced 'legacy-android-test' with 'android.test.base' and 'android.test.runner' in LOCAL_JAVA_LIBRARIES because AppLaunch's source depends on their classes. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that AppLaunch specifies in its manifest. * tests/Camera2Tests/SmartCamera/SimpleCamera/tests/Android.mk Replaced 'legacy-android-test' with 'android.test.base' in LOCAL_JAVA_LIBRARIES because SmartCamera-tests's source depends on its classes. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that SmartCamera-tests specifies in its manifest. * tests/ServiceCrashTest/Android.mk Replaced 'legacy-android-test' with 'android.test.base' in LOCAL_JAVA_LIBRARIES because ServiceCrashTest's source depends on its classes. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that ServiceCrashTest specifies in its manifest. * tests/net/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because FrameworksNetTests's source depends on their classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksNetTests specifies in its manifest. * tests/testables/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because testables is not a package so does not need to statically include the classes Added 'android.test.mock' to LOCAL_JAVA_LIBRARIES because testables has a source dependency on its classes * tests/utils/testutils/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because frameworks-base-testutils is not a package so does not need to statically include the classes Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because frameworks-base-testutils has a source dependency on their classes * wifi/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksWifiApiTests's source depends on its classes and because of these changes they are no longer present on the compilation path. The classes do not need to be statically included because the classes will be provided by the runtime, either from the default bootclasspath or from the android.test.runner library that FrameworksWifiApiTests specifies in its manifest. Bug: 30188076 Test: make checkbuild Change-Id: Ia6a48234f28e7e1789049cf4b37cd7fe0bc8251c
/frameworks/base/wifi/tests/Android.mk
|
607c4accb50008c1322cf9c0c686b645c2aab110 |
|
18-Aug-2017 |
Stephen Chen <stewchen@google.com> |
Use a LruCache in WifiNetworkScoreCache. Bug: 19948759 Test: runtest --path frameworks/base/wifi/tests/src/android/net/wifi/WifiNetworkScoreCacheTest.java Change-Id: I60bab6c2540df9819180d81d4e8e885066d92f51
/frameworks/base/wifi/tests/Android.mk
|
a1dff7719602bad1d98d241442008c006ed9cc59 |
|
06-Jul-2017 |
Etan Cohen <etancohen@google.com> |
[P2P] Public API to clean-up resources of P2P 1. Add public API to close a Channel and allow configuration to be cleaned-up. Actual clean-up will only happen when the last p2p client executes close or terminates (binder death is triggered for the service). 2. Add Close Guard to verify that API is called - issue warning otherwise. Note that to actually get the warning an app needs to use the StrictMode policy: StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder() .detectLeakedClosableObjects().build()); Bug: 37443149 Test: (new) unit tests, CtsVerifier, Settings/WFD app Change-Id: I9590101ef7f7ba0a90812634ac1b931d1482fe72
/frameworks/base/wifi/tests/Android.mk
|
473a16e492f0e0b0f726d4351214783458466d2c |
|
15-Mar-2017 |
Simran Basi <sbasi@google.com> |
frameworks/base: Add APCT tests to the device-tests suite. This CL adds the APCT tests within this project to a similar suite as CTS known as device-tests. The current method of running APCT tests in the infrastructure is unaffected. Bug: 35882476 Test: `make dist device-tests -j` and local builds of continuous_instrumentation_tests & continuous_native_tests Change-Id: Ifa382fe691842c1cd76897775b9e2a1653449eb5
/frameworks/base/wifi/tests/Android.mk
|
46169f946bc50627799719930cf07750c6926a80 |
|
30-Nov-2016 |
Sundeep Ghuman <sghuman@google.com> |
Copy WifiNetworkScoreCache into frameworks/base. Add tests. Begin process of migrating WifiNetworkScoreCache.java from System Server (//frameworks/opt/net/wifi/service/java/com/android/server/wifi/) to a SystemApi. This CL is a straight copy and paste of WifiNetworkScoreCache.java. Only new code is located in WifiNetworkScoreCacheTest.java Bug: b/33050254 Test: Unit tests added to cover most common use cases. Change-Id: I7510420d293339ce7811fcf71a6efceb8d809c3a
/frameworks/base/wifi/tests/Android.mk
|
601964b92795860610262cabfc920765d174fd93 |
|
26-Sep-2016 |
Peter Qiu <zqiu@google.com> |
wifi: add test target/directory for unit testing WiFi framework APIs The existing tests for the WiFi frameworks API android.net.wifi are copied from frameworks/opt/wifi/tests, and will be removed in frameworks/opt/wifi/tests. Bug: 31745421 Change-Id: I789e983bc7dd02b6c3fa6a982ca671347912be0f Test: frameworks/base/wifi/runtests.sh
/frameworks/base/wifi/tests/Android.mk
|