Commit Graph

39 Commits

Author SHA1 Message Date
Brett Chabot
420804ce3e Migrate cts/tests/tests/net to androidx.test
See go/jetpack-test-android-migration

Test: m -j CtsNetTestCases
Change-Id: I4a76e9b9410f94e297bca4287f450fe3b72fb409
Merged-In: If102677e4cdc4361b5d93283c4d6140dc477a94a
2019-03-01 21:09:26 +00:00
Paul Duffin
7131af6b93 Add tests for InetAddresses.parseNumericAddress()
Test: run cts -m CtsNetTestCases
Bug: 78686891
Change-Id: I1e121ab3fd619964625c4b51e0b7280eef001775
2018-12-17 15:46:26 +00:00
Neil Fuller
0b72fa9cfe Remove explicit dependency on conscrypt
The dependency is unnecessary as by default conscrypt
is included in the "standard libraries".

Test: build
Bug: 113148576
Change-Id: I30d68049215c61931bdd7aa5e2a0f125e6d1bf90
2018-10-11 16:11:37 +01:00
Ricky Wai
087de1c815 Set empty watchlist test config before CTS
Test: CTS pass
Bug: 63908748
Change-Id: I8b607feb44f873aced1ae3c2ff02c02f0553fb10
2018-03-30 23:56:35 +00:00
Anton Hansson
9a9ceeff6a cts: 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
Change-Id: I5afdfc8e1e523768db9065dd3571cb31bc1dfac5
2018-02-23 11:11:11 +00:00
Jiyong Park
e2fea86b44 Use stubs libs for android.test.base/runner/mock
android.test.base/runner/mock libraries are shared libraries that are
built without SDK, but with framework interanl libraries (framework.jar,
etc). Apps or libs that are built with SDK (LOCAL_SDK_VERSION is set)
shouldn't use them, but instead the stubs version of the test framework
libraries, which are built using SDK.

This is because, the build system does not allow a module built with SDK
to depend on another module built without SDK. This has been
exceptionally allowed with warnings, but will soon be errors.

In order to prevent the expected build breakage, direct reference to the
shared libraries are all changed to the stubs libraries.

Note: no one has been using these shared libs statically. So, it is
guaranteed that they won't encounter a problem due to missing
<uses-library name="android.test.runner"/> even after this change.

Bug: 69899800
Test: m -j checkbuild
Change-Id: I278fcf0b7f4972c473462eb88c46a111b0ce7d89
2018-01-24 17:15:49 +09:00
Paul Duffin
bed51fc9b9 Stop statically including legacy-android-test
Statically including legacy-android-test leads to duplicate classes
which causes build time problems (with Proguard) and runtime problems on
older SDK versions. This change:
* Stops statically including legacy-android-test.
* Adds compile time dependencies on andoid.test.base, android.test.mock
  and android.test.runner where necessary.
* Adds <uses-library android:name="android.test.runner"/> to any
  affected package to ensure that the classes that were included by
  legacy-android-test are still available at runtime. That also adds a
  dependency on android.test.base and android.test.mock.

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.

* hostsidetests/abioverride/app/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAbiOverrideTestApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/abioverride/app/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAbiOverrideTestApp at runtime.

* hostsidetests/appsecurity/test-apps/AccessSerialModern/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAccessSerialModern
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/AccessSerialModern/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAccessSerialModern at runtime.

* hostsidetests/appsecurity/test-apps/AppAccessData/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAppAccessData
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/AppWithData/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAppWithData results
    in duplicate classes which leads to build time and compile time
    issues.

* hostsidetests/appsecurity/test-apps/DocumentProvider/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDocumentProvider
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/DocumentProvider/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsDocumentProvider at runtime.

* hostsidetests/appsecurity/test-apps/EphemeralTestApp/EphemeralApp1/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsEphemeralTestsEphemeralApp1's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsEphemeralTestsEphemeralApp1 results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/EphemeralTestApp/ImplicitlyExposedApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsEphemeralTestsImplicitApp results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/EphemeralTestApp/NormalApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsEphemeralTestsNormalApp results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsEphemeralTestsNormalApp's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* hostsidetests/appsecurity/test-apps/EphemeralTestApp/UserApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsEphemeralTestsUserApp results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/EphemeralTestApp/UserAppTest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsEphemeralTestsUserAppTest results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/ExternalStorageApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsExternalStorageApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/InstrumentationAppDiffCert/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsInstrumentationAppDiffCert results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/MultiUserStorageApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsMultiUserStorageApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/ReadExternalStorageApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsReadExternalStorageApp results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsReadExternalStorageApp's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* hostsidetests/appsecurity/test-apps/SplitApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSplitApp results in
    duplicate classes which leads to build time and compile time
    issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsSplitApp's source depends on its classes and because of these
    changes they are no longer present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSplitAppDiffRevision
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsSplitAppDiffRevision's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSplitAppDiffVersion
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsSplitAppDiffVersion's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSplitAppDiffCert
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsSplitAppDiffCert's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* hostsidetests/appsecurity/test-apps/StorageAppA/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsStorageAppA results
    in duplicate classes which leads to build time and compile time
    issues.

* hostsidetests/appsecurity/test-apps/StorageAppB/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsStorageAppB results
    in duplicate classes which leads to build time and compile time
    issues.

* hostsidetests/appsecurity/test-apps/StorageStatsApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsStorageStatsApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/appsecurity/test-apps/UsePermissionApp23/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUsePermissionApp23
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsUsePermissionApp23
    targets SDK version 23 which provides all the classes at runtime.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsUsePermissionApp23's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* hostsidetests/appsecurity/test-apps/UsePermissionApp23/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsUsePermissionApp23 at runtime.

* hostsidetests/appsecurity/test-apps/UsePermissionApp25/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUsePermissionApp25
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsUsePermissionApp25
    targets SDK version 25 which provides all the classes at runtime.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsUsePermissionApp25's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* hostsidetests/appsecurity/test-apps/UsePermissionApp25/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsUsePermissionApp25 at runtime.

* hostsidetests/appsecurity/test-apps/UsePermissionApp26/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUsePermissionApp26
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsUsePermissionApp26
    targets SDK version 26 which provides all the classes at runtime.

* hostsidetests/appsecurity/test-apps/UsePermissionApp26/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsUsePermissionApp26 at runtime.

* hostsidetests/appsecurity/test-apps/UsePermissionAppLatest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsUsePermissionAppLatest results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/UsePermissionAppLatest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsUsePermissionAppLatest at runtime.

* hostsidetests/appsecurity/test-apps/UsePermissionDiffCert/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsUsePermissionDiffCert results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/appsecurity/test-apps/WriteExternalStorageApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsWriteExternalStorageApp results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsWriteExternalStorageApp's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* hostsidetests/appsecurity/test-apps/keysets/testApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsKeySetTestApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/AccountCheck/Auth/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAccountCheckAuthApp
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsAccountCheckAuthApp
    targets SDK version 25 which provides all the classes at runtime.

* hostsidetests/devicepolicy/app/AccountCheck/Auth/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAccountCheckAuthApp at runtime.

* hostsidetests/devicepolicy/app/AccountManagement/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAccountManagementDevicePolicyApp results in duplicate classes
    which leads to build time and compile time issues.

* hostsidetests/devicepolicy/app/AccountManagement/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAccountManagementDevicePolicyApp at runtime.

* hostsidetests/devicepolicy/app/Assistant/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsDevicePolicyAssistApp results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/devicepolicy/app/Assistant/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsDevicePolicyAssistApp at runtime.

* hostsidetests/devicepolicy/app/CrossProfileAppsTest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsCrossProfileAppsTests results in duplicate classes which leads
    to build time and compile time issues. It is also unnecessary as
    CtsCrossProfileAppsTests targets SDK version 25 which provides all
    the classes at runtime.

* hostsidetests/devicepolicy/app/CustomizationApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsCustomizationApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/CustomizationApp/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsCustomizationApp at runtime.

* hostsidetests/devicepolicy/app/DelegateApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDelegateApp results
    in duplicate classes which leads to build time and compile time
    issues.

* hostsidetests/devicepolicy/app/DeviceAdmin/api23/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDeviceAdminApp23
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsDeviceAdminApp23 targets
    SDK version 23 which provides all the classes at runtime.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsDeviceAdminApp23's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* hostsidetests/devicepolicy/app/DeviceAdmin/api24/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDeviceAdminApp24
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsDeviceAdminApp24 targets
    SDK version 24 which provides all the classes at runtime.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsDeviceAdminApp24's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* hostsidetests/devicepolicy/app/DeviceOwner/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDeviceOwnerApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/IntentReceiver/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsIntentReceiverApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/IntentSender/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsIntentSenderApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/LauncherTests/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsLauncherAppsTests
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsLauncherAppsTests targets
    SDK version 25 which provides all the classes at runtime.

* hostsidetests/devicepolicy/app/ManagedProfile/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsManagedProfileApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/PackageInstaller/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPackageInstallerApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/ProfileOwner/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsProfileOwnerApp
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/SingleAdminApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsDevicePolicySingleAdminTestApp results in duplicate classes
    which leads to build time and compile time issues.

* hostsidetests/devicepolicy/app/WifiConfigCreator/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsWifiConfigCreator
    results in duplicate classes which leads to build time and compile
    time issues.

* hostsidetests/devicepolicy/app/WifiConfigCreator/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsWifiConfigCreator at runtime.

* hostsidetests/dumpsys/apps/ProcStatsHelperApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsProcStatsHelperApp
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsProcStatsHelperApp
    targets SDK version 24 which provides all the classes at runtime.

* hostsidetests/dumpsys/apps/ProcStatsHelperApp/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsProcStatsHelperApp at runtime.

* hostsidetests/media/app/MediaSessionTest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsMediaSessionHostTestApp results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/media/app/MediaSessionTest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsMediaSessionHostTestApp at runtime.

* hostsidetests/numberblocking/app/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsHostsideNumberBlockingAppTest results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/os/test-apps/StaticSharedLibConsumerApp1/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsStaticSharedLibConsumerApp1 results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/os/test-apps/StaticSharedLibConsumerApp1/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsStaticSharedLibConsumerApp1 at runtime.

* hostsidetests/shortcuts/deviceside/backup/launcher1/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupLauncher1 results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/launcher1/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupLauncher1 at runtime.

* hostsidetests/shortcuts/deviceside/backup/launcher2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupLauncher2 results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/launcher2/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupLauncher2 at runtime.

* hostsidetests/shortcuts/deviceside/backup/launcher3/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupLauncher3 results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/launcher3/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupLauncher3 at runtime.

* hostsidetests/shortcuts/deviceside/backup/launcher4new/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupLauncher4new results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/launcher4new/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupLauncher4new at runtime.

* hostsidetests/shortcuts/deviceside/backup/launcher4old/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupLauncher4old results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/launcher4old/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupLauncher4old at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher1/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher1 results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher1/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher1 at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher2 results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher2/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher2 at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher3/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher3 results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher3/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher3 at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4new/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4new results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4new/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4new at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_nobackup/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4new_nobackup results in duplicate
    classes which leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_nobackup/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4new_nobackup at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_nomanifest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4new_nomanifest results in duplicate
    classes which leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_nomanifest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4new_nomanifest at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_wrongkey/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4new_wrongkey results in duplicate
    classes which leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4new_wrongkey/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4new_wrongkey at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4old/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4old results in duplicate classes which
    leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4old/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4old at runtime.

* hostsidetests/shortcuts/deviceside/backup/publisher4old_nomanifest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutBackupPublisher4old_nomanifest results in duplicate
    classes which leads to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/backup/publisher4old_nomanifest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutBackupPublisher4old_nomanifest at runtime.

* hostsidetests/shortcuts/deviceside/multiuser/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutMultiuserTest results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/multiuser/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutMultiuserTest at runtime.

* hostsidetests/shortcuts/deviceside/upgrade/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutUpgradeVersion1 results in duplicate classes which leads
    to build time and compile time issues.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutUpgradeVersion2 results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/shortcuts/deviceside/upgrade/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutUpgradeVersion1 at runtime.

* hostsidetests/ui/appA/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsDeviceTaskSwitchingAppA results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/ui/appA/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsDeviceTaskSwitchingAppA at runtime.

* hostsidetests/ui/appB/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsDeviceTaskSwitchingAppB results in duplicate classes which leads
    to build time and compile time issues.

* hostsidetests/ui/appB/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsDeviceTaskSwitchingAppB at runtime.

* hostsidetests/usb/SerialTestApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUsbSerialTestApp
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/JobScheduler/jobperm/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsJobSchedulerJobPerm
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/JobScheduler/jobperm/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsJobSchedulerJobPerm at runtime.

* tests/JobScheduler/shareduid/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsJobSchedulerSharedUid results in duplicate classes which leads
    to build time and compile time issues.

* tests/JobScheduler/shareduid/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsJobSchedulerSharedUid at runtime.

* tests/ProcessTest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in ProcessTests results in
    duplicate classes which leads to build time and compile time
    issues.

* tests/acceleration/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAccelerationTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsAccelerationTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/accessibilityservice/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAccessibilityServiceTestCases results in duplicate classes which
    leads to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsAccessibilityServiceTestCases's source depends on its classes
    and because of these changes they are no longer present on the
    compilation path.

* tests/admin/app/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAdminApp results in
    duplicate classes which leads to build time and compile time
    issues.

* tests/app/app/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsAppTestStubs's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAppTestStubs results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/app/app2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAppTestStubsDifferentUid results in duplicate classes which
    leads to build time and compile time issues.

* tests/app/app2/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAppTestStubsDifferentUid at runtime.

* tests/backup/app/fullbackup/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsFullBackupApp
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/backup/app/fullbackup/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to CtsFullBackupApp
    at runtime.

* tests/backup/app/keyvalue/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsKeyValueBackupApp
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/backup/app/keyvalue/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsKeyValueBackupApp at runtime.

* tests/fragment/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsFragmentTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/framework/base/windowmanager/alertwindowservice/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAlertWindowService
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/framework/base/windowmanager/alertwindowservice/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsAlertWindowService at runtime.

* tests/jank/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsJankDeviceTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsJankDeviceTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/leanbackjank/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsLeanbackJankTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsLeanbackJankTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/leanbackjank/app/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsLeanbackJankApp
    results in duplicate classes which leads to build time and compile
    time issues. It is also unnecessary as CtsLeanbackJankApp targets
    SDK version 23 which provides all the classes at runtime.

* tests/leanbackjank/app/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsLeanbackJankApp at runtime.

* tests/netlegacy22.api/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetTestCasesLegacyApi22 results in duplicate classes which leads
    to build time and compile time issues.

* tests/netlegacy22.permission/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetTestCasesLegacyPermission22 results in duplicate classes
    which leads to build time and compile time issues.

* tests/pdf/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPdfTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/sample/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsSampleDeviceTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsSampleDeviceTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/tests/accounts/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAccountManagerTestCases results in duplicate classes which leads
    to build time and compile time issues. It is also unnecessary as
    CtsAccountManagerTestCases targets SDK version 26 which provides
    all the classes at runtime.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsAccountManagerTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/tests/animation/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAnimationTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/app.usage/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUsageStatsTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' and 'android.test.runner' to
    LOCAL_JAVA_LIBRARIES because CtsUsageStatsTestCases's source
    depends on their classes and because of these changes they are no
    longer present on the compilation path.

* tests/tests/app/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsAndroidAppTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAndroidAppTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/appwidget/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsAppWidgetTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsAppWidgetTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/bluetooth/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsBluetoothTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/calendarcommon/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsCalendarcommon2TestCases results in duplicate classes which
    leads to build time and compile time issues. It is also unnecessary
    as CtsCalendarcommon2TestCases targets SDK version 15 which
    provides all the classes at runtime.

* tests/tests/car/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsCarTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/tests/carrierapi/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsCarrierApiTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsCarrierApiTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/colormode/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsColorModeTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/content/Android.mk
    Added 'android.test.base' and 'android.test.mock' to
    LOCAL_JAVA_LIBRARIES because CtsContentTestCases's source depends
    on their classes and because of these changes they are no longer
    present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsContentTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/database/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDatabaseTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/display/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDisplayTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/dpi/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDpiTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsDpiTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/dreams/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDreamsTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsDreamsTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/drm/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsDrmTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/tests/dynamic_linker/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsDynamicLinkerTestCases results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/externalservice/service/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsExternalServiceService results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/externalservice/service/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsExternalServiceService at runtime.

* tests/tests/graphics/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsGraphicsTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/hardware/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsHardwareTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsHardwareTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/incident/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsIncidentTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/keystore/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsKeystoreTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsKeystoreTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/libcorefileio/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsLibcoreFileIOTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsLibcoreFileIOTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/tests/location2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsLocation2TestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsLocation2TestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/media/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsMediaTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsMediaTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/net/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsNetTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsNetTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/tests/netsecpolicy/usescleartexttraffic-false/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetSecPolicyUsesCleartextTrafficFalseTestCases results in
    duplicate classes which leads to build time and compile time
    issues.

* tests/tests/netsecpolicy/usescleartexttraffic-true/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetSecPolicyUsesCleartextTrafficTrueTestCases results in
    duplicate classes which leads to build time and compile time
    issues.

* tests/tests/netsecpolicy/usescleartexttraffic-unspecified/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetSecPolicyUsesCleartextTrafficUnspecifiedTestCases results in
    duplicate classes which leads to build time and compile time
    issues.

* tests/tests/networksecurityconfig/networksecurityconfig-downloadmanager/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetSecConfigDownloadManagerTestCases results in duplicate
    classes which leads to build time and compile time issues.

* tests/tests/networksecurityconfig/networksecurityconfig-resourcesrc/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsNetSecConfigResourcesSrcTestCases results in duplicate classes
    which leads to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsNetSecConfigResourcesSrcTestCases's source depends on its
    classes and because of these changes they are no longer present on
    the compilation path.

* tests/tests/opengl/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsOpenGLTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsOpenGLTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/os/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsOsTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsOsTestCases's source depends on its classes and because of these
    changes they are no longer present on the compilation path.

* tests/tests/packageinstaller/adminpackageinstaller/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsAdminPackageInstallerTestCases results in duplicate classes
    which leads to build time and compile time issues.

* tests/tests/permission/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPermissionTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsPermissionTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/permission2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPermission2TestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/preference/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPreferenceTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsPreferenceTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/preference2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPreference2TestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsPreference2TestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/renderscript/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsRenderscriptTestCases results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/rsblas/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsRsBlasTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/rscpp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsRsCppTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/sax/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSaxTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

* tests/tests/security/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSecurityTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsSecurityTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/selinux/selinuxTargetSdk2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsSelinuxTargetSdk2TestCases results in duplicate classes which
    leads to build time and compile time issues.

* tests/tests/shortcutmanager/packages/launchermanifest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerLauncher1 results in duplicate classes which
    leads to build time and compile time issues.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerLauncher2 results in duplicate classes which
    leads to build time and compile time issues.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerLauncher3 results in duplicate classes which
    leads to build time and compile time issues.

* tests/tests/shortcutmanager/packages/launchermanifest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutManagerLauncher1 at runtime.

* tests/tests/shortcutmanager/packages/launchermanifest_nonshared/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerLauncher4 results in duplicate classes which
    leads to build time and compile time issues.

* tests/tests/shortcutmanager/packages/launchermanifest_nonshared/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutManagerLauncher4 at runtime.

* tests/tests/shortcutmanager/packages/packagemanifest/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerPackage1 results in duplicate classes which leads
    to build time and compile time issues.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerPackage2 results in duplicate classes which leads
    to build time and compile time issues.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerPackage3 results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/shortcutmanager/packages/packagemanifest/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutManagerPackage1 at runtime.

* tests/tests/shortcutmanager/packages/packagemanifest_nonshared/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerPackage4 results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/shortcutmanager/packages/packagemanifest_nonshared/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutManagerPackage4 at runtime.

* tests/tests/shortcutmanager/throttling/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsShortcutManagerThrottlingTest results in duplicate classes which
    leads to build time and compile time issues. It is also unnecessary
    as CtsShortcutManagerThrottlingTest targets SDK version 25 which
    provides all the classes at runtime.

* tests/tests/shortcutmanager/throttling/AndroidManifest.xml
    Add uses-library for android.test.runner because otherwise this
    change would change the set of files available to
    CtsShortcutManagerThrottlingTest at runtime.

* tests/tests/simpleperf/CtsSimpleperfDebugApp/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSimpleperfDebugApp
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/slice/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSliceTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/speech/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSpeechTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsSpeechTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tests/tests/systemintents/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsSystemIntentTestCases results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/systemui/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsSystemUiTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/telecom/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsTelecomTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/telecom2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsTelecomTestCases2
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/telephony/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsTelephonyTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsTelephonyTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/telephony2/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsTelephony2TestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsTelephony2TestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/theme/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsThemeDeviceTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsThemeDeviceTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/transition/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsTransitionTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/uiautomation/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsUiAutomationTestCases results in duplicate classes which leads
    to build time and compile time issues.

* tests/tests/uidisolation/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsUidIsolationTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsUidIsolationTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/tests/uirendering/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUiRenderingTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/util/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsUtilTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/view/Android.mk
    Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because
    CtsViewTestCases's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsViewTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/widget/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsWidgetTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

* tests/tests/wrap/nowrap/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsWrapNoWrapTestCases
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsWrapNoWrapTestCases's source depends on its classes and because
    of these changes they are no longer present on the compilation
    path.

* tests/tests/wrap/wrap_debug/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsWrapWrapDebugTestCases results in duplicate classes which leads
    to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsWrapWrapDebugTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/tests/wrap/wrap_debug_malloc_debug/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsWrapWrapDebugMallocDebugTestCases results in duplicate classes
    which leads to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsWrapWrapDebugMallocDebugTestCases's source depends on its
    classes and because of these changes they are no longer present on
    the compilation path.

* tests/tests/wrap/wrap_nodebug/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in
    CtsWrapWrapNoDebugTestCases results in duplicate classes which
    leads to build time and compile time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsWrapWrapNoDebugTestCases's source depends on its classes and
    because of these changes they are no longer present on the
    compilation path.

* tests/vr/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsVrTestCases results
    in duplicate classes which leads to build time and compile time
    issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsVrTestCases's source depends on its classes and because of these
    changes they are no longer present on the compilation path.

* tools/cts-holo-generation/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsHoloGeneration
    results in duplicate classes which leads to build time and compile
    time issues.

    Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because
    CtsHoloGeneration's source depends on its classes and because of
    these changes they are no longer present on the compilation path.

* tools/cts-preconditions/Android.mk
    Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES
    because statically including the classes in CtsPreconditions
    results in duplicate classes which leads to build time and compile
    time issues.

Bug: 30188076
Test: make checkbuild
Change-Id: I56c62344ab09338ed35586d76c0440d6f9515d72
2017-12-08 00:07:01 +00:00
nickrose
02fa5a5648 Add all CTS tests to VTS, to improve VTS coverage.
b/62423436.

This CL was generated using the following command:
master/cts$ grep -rl "LOCAL_COMPATIBILITY_SUITE := cts" . | \
xargs sed -i \
's/LOCAL_COMPATIBILITY_SUITE := cts/LOCAL_COMPATIBILITY_SUITE := cts vts/g'

Based on change: d98ea4bc2a

Test: make vts -j32
Verified VTS output contained the CTS test case source code.

Change-Id: Id52ac1639447276171006c33bdfa7b4e6c874745
2017-07-07 12:28:36 -07:00
Simran Basi
d98ea4bc2a cts: Add all tests to general-tests
Adds all the cts tests to general-tests so they can will
be included in the general-tests.zip file.

This cl was generated using the following command:
master/cts$ grep -rl "LOCAL_COMPATIBILITY_SUITE := cts" . | \
xargs sed -i \
's/LOCAL_COMPATIBILITY_SUITE := cts/LOCAL_COMPATIBILITY_SUITE := cts general-tests/g'

Bug: None
Test: make general-tests -j
Change-Id: Idbddf1560a31961cb2e6cab8cf55b55e22ecbbff
2017-04-24 12:28:16 -07:00
Paul Duffin
038b6a4374 Prepare for removal of legacy-test from default targets
In preparation for removing junit classes from the Android API
the legacy-test target will be removed from the
TARGET_DEFAULT_JAVA_LIBRARIES. This change adds explicit
dependencies on junit and/or legacy-android-test to ensure that
modules will compile properly once it is removed.

Bug: 30188076
Test: make checkbuild
Change-Id: I0f34fe97154240e8f8eef6816df1c794da60351e
2017-01-20 11:22:59 +00:00
Aaron Holden
37698cb72b Move libs/deviceutil to device-side/util
Test: build cts, run unit tests
bug:21762834
Change-Id: Ifd164ced7f040e312e3553f27adf59a648f463ab
2016-12-12 12:27:20 -08:00
Stuart Scott
a9e563cf83 Switch to CTSv2
bug:21762834
Change-Id: Ie51a0ed4560b46c2f360e14980e5fab7fe6479fe
2016-02-29 21:51:59 -08:00
Dimitry Ivanov
a907d75f06 Merge "Untie MultinetworkApiTest from platform libc++.so" am: 2e14e9afaa am: 4577e05c13
am: 5a78c96856

* commit '5a78c968564520b256ea1e23e36c4b11ca130bc4':
  Untie MultinetworkApiTest from platform libc++.so
2016-01-13 18:54:39 +00:00
Dimitry Ivanov
04d19df9ca Untie MultinetworkApiTest from platform libc++.so
Bug: http://b/26512135
Change-Id: Ia01fd851fd7d2e50708620adf11d904e42de0b3b
2016-01-12 12:19:12 -08:00
Nash Lincoln
de95223f87 migrate net tests to cts_v2
bug:21762834
Change-Id: Ic86dee963720c1412a42ec231c81c97d7f322420
2015-09-17 13:46:25 -07:00
Erik Kline
1c542daddb multinetwork native API CTS test
Bug: 19537384
Bug: 21833352
Change-Id: I03df80beca241fe3c952aae65de0cd081751de07
2015-06-24 18:10:07 +09:00
Narayan Kamath
505728b35a Add explicit dependencies on org.apache.http.legacy
Test modules that depend on the CTS testserver must declare
explicit dependencies on org.apache.http.legacy.

Also fix some bizarre build rules; ctstestserver builds directly
against the framework but compiled into apps that target SDK 16.

bug: 18027885

Change-Id: I905942d8ed71812499df94e3e5970c0b08716528
2015-02-06 13:56:30 +00:00
Neil Fuller
51130c9726 Add HttpResponseCacheTest as a CTS test
Moving HttpResponseCacheTest.java from
frameworks/base/core/tests/coretests/src/android/net/http
to
cts/tests/tests/net/src/android/net/http/cts

And making it work in the CTS runner by setting
temp directory permissions and making sure the
cache is initialized.

Change-Id: I032014789f27a66c1a7a0aee0fa0494f6041238e
2015-01-15 16:51:48 +00:00
Unsuk Jung
94995b1dc8 Build CTS tests as multilib apks
CTS-tradefed uses the same apk for both 32 and 64 bit tests.

Bug: 17924614
Change-Id: Idbf2d93c54efbb1c281ad9e93f0f39430614df61
2014-10-09 01:08:48 -07:00
Brett Chabot
cf8d741f3d Move to android.support.test as CTS instrumentation runner.
Also do the following related cleanup
- Remove references to deprecated BrokenTest and KnownFailure
- Switch CTS tests to build against SDK and not private
android.test.runner where possible

Bug: 12924356

Change-Id: If6151b836456eec4838f8d7d6e11c9834c007fca
2014-03-11 17:54:45 -07:00
Alex Klyubin
99de4e3610 am 7d0d1c56: am 38866e37: Merge "Test default config of SSLCertificateSocketFactory."
* commit '7d0d1c560d28591b4533ee1bfe830a6ec535f697':
  Test default config of SSLCertificateSocketFactory.
2014-01-22 19:49:06 +00:00
Alex Klyubin
652d30b4b5 Test default config of SSLCertificateSocketFactory.
Bug: 11220570
Change-Id: I37440f3e8eda18215b9af703c027e4c8ca0334bf
2014-01-16 14:52:46 -08:00
William Luh
e57a5f7b6f Merge "CTS test for X509TrustManagerExtensions.isUserAddedCertificate." 2013-12-13 18:21:53 +00:00
William Luh
638d1eeee7 CTS test for X509TrustManagerExtensions.isUserAddedCertificate.
Bug: 11257762
Change-Id: I4d8bec7b75613b3286063e28b0fe0cba4e5c716b
2013-11-12 10:05:11 -08:00
Stuart Scott
7fd24cb8df Refactoring CTS to remove PTS references.
PTS is now a part of CTS

bug: 11561456
Change-Id: I577296fe7735790e285aa4747dc7832bc8ae5b6d
2013-11-08 14:29:01 -08:00
Robert Greenwalt
9ac09493ad Add Dns CTS test.
Checks java and native calls.
Adds some performance tests, but need to look at how that should be used.

Change-Id: I158164829da13302d9532275cef3482c4736168e
2013-02-14 12:04:46 -08:00
Wink Saville
775417bd58 Delete frameworks/base/voip use voip-common from frameworks/opt/net/voip
Change-Id: Ieaba759a0f69b45c4b8839cbed1fe757cdf190c5
2013-01-28 20:00:57 -08:00
Keun young Park
30199405c3 change testRunner to CtsTestRunner
- unlock keyguard by default

Change-Id: I0452a72cfa54edfa79b485894ffd0493a71122ee
2012-07-12 12:57:30 -07:00
Brian Muramatsu
237e076594 Fix WifiInfoTest flakiness
Poll a bit longer waiting for getNetworkId and getWifiState to return
the proper values. The bug reports seem to indicate that the WiFi
is shutting down properly.

Add a new static check method to PollingCheck that I think is simpler
than the existing way of creating a new PollingCheck, overriding
check, and then making sure to call run. This new variation also allows
you to specify a message rather than just "unexpected timeout."

Bug 6443337

Change-Id: I9f7c942f6e26b957bb717b58b1ab984acc556bf7
2012-06-26 15:05:08 -07:00
Brian Muramatsu
248128f2a9 Static Libs for Popular CTS Stub Components
com.android.cts.stub is growing very large. Split apart some of
the popular components into separate static libraries. This
should allow packages to depend on the components they need
rather than all of cts.stub.

Current code at the moment doesn't have to be changed, because
I have CtsTestStubs depending on these new shared libraries.
However, change the net package to depend on the ctstestserver
static library as a proof of concept rather than including
its source directly.

Change-Id: I32c54eab3ddfb1d4391d6ffc347fbc9cb2fe97f9
2012-03-05 18:46:33 -08:00
Chia-chi Yeh
e4791afe6c am b57076f9: am edd2f178: am 4231515a: Free net.cts from cts.stub.
* commit 'b57076f9137e2acd6fb9145b8f8be26f43d91cdb':
  Free net.cts from cts.stub.
2012-02-28 15:40:30 -08:00
Chia-chi Yeh
4231515a1b Free net.cts from cts.stub.
Explicitly include CtsTestServer in Android.mk to eliminate the
dependency to cts.stub. This allows net.cts to instrument itself,
and it also allows network-specific JNI code to be added in the
same package.

Change-Id: I624f87e0112619c5b97f2c3589933f666665fa8e
2012-02-28 14:58:23 -08:00
Brian Muramatsu
59be169eb9 Move Test XML Generation from buildCts.py
buildCts.py was the central script that generated all the
test package XMLs each time CTS was built. This had a
couple problems:

1. All the XML files for ~40 packages needed to be made
   every time CTS was made. Even if those packages were
   not touched at all.

2. Couldn't shard the XML generation process across the
   available cores on a machine. A pool was added to the
   python script, but it was set to a fixed number.

This change moves the test XML generation into a
smaller Java program called "cts-java-scanner" and
the doclet it relies upon to scan the Java files
into "cts-java-scanner-doclet.jar". The output of
the scanner like "cts-native-scanner" for native EXEs
is piped to the existing cts-xml-generator to
produce the test XMLs.

New CTS specific rules replace the standard
BUILD_PACKAGE and BUILD_HOST_JAVA_LIBRARY. They just
add extra rules for the package XML. The BUILD_CTS_PACKAGE
rule also adds a rule for copying the "package.apk"
to something more like "CtsFooTestCases.apk" to the
test case out directory. All the apks, exes, and xmls
are now thrown into a "cts-testcases" directory, before
they are copied to the final CTS distribution.

This change should prevent rebuilding the XMLs
unnecessarily and make rebuilding CTS quicker while
writing tests.

There are still the libcore tests that are always rebuilt,
but they can be adapted to fit into this model someday...

Change-Id: I52a916aa37fd679057e2709bb0ccec694c9fca01
2012-01-05 11:43:00 -08:00
Brett Chabot
dcccc54888 Change CTS tests to not build against SDK.
Most CTS test packages reference test related annotations in dalvik.annotation
which are not part of SDK. This was previously allowed due to bug in build
build system. For now, temporarily change CTS makefiles so they are not built
against SDK.

BUG 2114936
2009-09-11 15:31:30 -07:00
Brett Chabot
1505142f7b Change CTS makefiles so apps are built in data not system partition.
BUG 2053298

Change-Id: I2c541c03f7c33c69cde7b0567b080710658c8d28
2009-08-28 14:19:28 -07:00
Brett Chabot
f4ffdb9732 Remove a bunch of unused CTS tests from continuous test build to save space.
BUG 2053298
2009-08-14 14:17:58 -07:00
Phil Dubach
3da72df159 AI 147060: am: CL 147059 CTS: Fix LOCAL_MODULE_TAGS for CTS tests
CTS tests should use local module tag 'tests' such that they are not built
  and included in the image by default.
  Original author: phillipd
  Merged from: //branches/cupcake/...

Automated import of CL 147060
2009-04-21 01:02:54 -07:00
The Android Open Source Project
3cae4df32a auto import from //branches/cupcake_rel/...@140373 2009-03-18 17:39:42 -07:00
The Android Open Source Project
8aa1b8f449 auto import from //branches/cupcake_rel/...@138607 2009-03-15 16:47:16 -07:00