Age | Commit message (Collapse) | Author |
|
|
|
|
|
Test: atest TelephonyManagerTest#testRequestModemActivityInfo
Bug: 170427831
Change-Id: I93b7a9fbd718fbd5ad4970b656bee338d3baf362
Merged-In: I93b7a9fbd718fbd5ad4970b656bee338d3baf362
|
|
* changes:
Move keystore perf tests out of CTS suite
Add MAC test for Strongbox.
Annotate Block cipher tests with NuggetOS specific bugs.
Add CTS tests for Strongbox AES and 3Des ciphers.
Move assumeStrongbox to TestUtils.
|
|
Bug: 170427831
Test: atest ModemActivityInfoTest
Change-Id: If307046e4f4d0e9baa7400d2fc5dcbe73e7756ef
Merged-In: If307046e4f4d0e9baa7400d2fc5dcbe73e7756ef
|
|
Add a new test suite for performance tests.
Include the perf tests in post submit so the tests don't get stale.
Fixes: 194359253
Test: atest CtsKeystoreTestCases
Test: atest CtsKeystorePerformanceTestCases
Change-Id: Iaedbc727857f4eb9967a5b6546493545d860bf25
|
|
Test: atest android.keystore.cts.StrongboxMacTest
Change-Id: I204026a6526541c9a3e484ea333e2fa079ca917f
Merged-In: I204026a6526541c9a3e484ea333e2fa079ca917f
|
|
It is known that NuggetOS Strongbox does not fulfill all of the
expectations as to when cipher text is to be generated.
This patch annotates the failing tests with known bugs.
This CL can be reverted as soon as NuggetOS has fixed the issues.
Bug: 194123581
Bug: 194126736
Bug: 194134040
Bug: 194134359
Test: echo cts/tests/tests/keystore/src/android/keystore/cts/Strongbox* | sed -e 's#cts/tests/tests/keystore/src/##g;s/\.java//g;s#/#\.#g' | xargs atest
Change-Id: I55ba108248e42d7d9a39b2dc4591e7b092cd7a91
Merged-In: I55ba108248e42d7d9a39b2dc4591e7b092cd7a91
|
|
Test: echo cts/tests/tests/keystore/src/android/keystore/cts/Strongbox* | sed -e 's#cts/tests/tests/keystore/src/##g;s/\.java//g;s#/#\.#g' | xargs atest
Change-Id: Ie3bcdafb0779c144e339417f47de476c19470257
Merged-In: Ie3bcdafb0779c144e339417f47de476c19470257
|
|
Test: N/A
Change-Id: I0ba33094aedc61edf0be8533f16cca237451b6e5
Merged-In: I0ba33094aedc61edf0be8533f16cca237451b6e5
|
|
|
|
Bug: 197217250
Change-Id: Ia8b24b3c993637c3a73213bbc820c1a231b7a06f
Merged-In: Ia8b24b3c993637c3a73213bbc820c1a231b7a06f
Test: No code changes made.
|
|
|
|
Test: build
Bug: 178498823
Change-Id: Idb565df4d03afe077cf1ddea6638501c8987075d
Merged-In: Idb565df4d03afe077cf1ddea6638501c8987075d
|
|
|
|
|
|
Bug: 198670656
Test: atest PkgInstallSignatureVerificationTest
Change-Id: Ic22326650be72bd0b0d6717508998a8fd80b4b24
|
|
|
|
|
|
I'mt not a stakeholder anymore, as all the contacts provider CTS has
moved out.
Test: treehugger
Change-Id: I0cfef1997ca2481d1aff27ab22cbc1b4b39dd1ac
|
|
|
|
Bug: 197230471
Test: build
Change-Id: If842f00819736bf6f111f44ec752ca2f815866b4
|
|
|
|
This test just checks the prop value.
All encryption-related CDD requirements still must be met,
Use case: ARC's device encryption is managed by the host OS (Chrome OS).
(b/136127632#comment10)
Bug: 169207445
Test: android.security.cts.EncryptionTest#testEncryption
Change-Id: Ic00bc5fb7d54f68950d8508961ad60082afa1211
(cherry picked from commit ecf46d77f55be04c3e69fd5cf84bb4269789acc9)
|
|
|
|
|
|
Bug: 197281325
Test: atest android.telephony.cts.TelephonyManagerTest#testGetPhoneCapabilityAndVerify
Change-Id: Ie33e66c9db2c6b6ec206bd071259fe3ee54f68b6
Merged-In: Ie33e66c9db2c6b6ec206bd071259fe3ee54f68b6
|
|
|
|
During testAutoGrantMultiplePermissionsInGroup
"PERMISSION_POLICY_AUTO_GRANT" permission is set, which is not
removed after test run. testDelegation checks for default permission,
hence causing it to fail.
Bug: 197712301
Test: run CtsDevicePolicyManagerTestCases pass
Change-Id: I8fbea147e7e741c242713f163143014f85bd3f4e
Merged-In: Iff10fc0e0a10b5593ae8e497cb3595b81d044c00
|
|
|
|
* Check if the lock task activity is running instead of checking if it is existing in recent tasks list
Bug: 194457268
Test: run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.MixedDeviceOwnerTest#testLockTaskAfterReboot
Test: run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.MixedDeviceOwnerTest#testLockTaskAfterReboot_tryOpeningSettings
Change-Id: I93d2f2b4e9f89f2283a0add45de56bea052e11d8
|
|
|
|
|
|
* changes:
CtsNdkBinderTestCases: disable interface header
CtsNdkBinderTestCases: don't freeze interface
|
|
This is a CP of aosp/1686440.
The dynamicmime test failures for wear devices are manyfold. To fix
these,
1) resolver dialog should not be used because it's not really a
dialog on WearOS. Some other widget should be used instead (the
button in our case). To distinguish between the normal case and
WearOS case, Utils class has to be reworked.
2) in case we run tests using adb over ssh tunnel, delay tolerance
and robustness of the Utils class have to be increased.
This patch addresses all 2 issues.
Bug: 185800520
Test: atest -c android.dynamicmime.cts.PreferredActivitiesTestCases
Change-Id: I770f3fde98e6bcb7da99d0abe32dd822e2edc351
|
|
Introduces a new manually-written class that doesn't use interface
header. Legacy code (or code not using AIDL, which should have different
ways of checking/encoding the object type) may not have a header, so
this tests AIBinder_Class_disableInterfaceTokenHeader.
Bug: 188022639
Test: CtsNdkBinderTestCases
Change-Id: I9d79f9c351582dfbd2921e78f816ae497e73b347
|
|
We only need the compat interface frozen.
Bug: 188022639
Test: CtsNdkBinderTestCases
Change-Id: I8d0371e28892f307376d4f12374734152772954c
Merged-In: I8d0371e28892f307376d4f12374734152772954c
|
|
AccessibilityGestureDispatchTest#testClickWhenMagnified_matchesActualTouch CTS test for foldable devices."
|
|
Build android-cts-verifier.zip in Soong, and export it to Make to
copy and unzip into $(HOST_OUT).
Bug: 197794946
Test: m out/host/linux-x86/cts-verifier/android-cts-verifier.zip
Change-Id: Ibf0e19e700de8583114598285e160d445fe2829d
Merged-In: Ibf0e19e700de8583114598285e160d445fe2829d
|
|
|
|
Our remote control is not supporting "Bluetooth Privacy Mode" we needed to deactivate it.
This leads to failure on these 2 CTS-V tests :
|---> Bluetooth LE Connection Priority Client Test
|---> Bluetooth LE Encrypted Client Test
Since these tests are not mandatory in Androi10, so we made a patch to disable them
Bug: 194428623
Bug: Bluetooth LE Secure Client Tests failed with Android10
Bug id https://partnerissuetracker.corp.google.com/u/1/issues/194428623
Test: Bluetooth LE Connection Priority Client Test and
Bluetooth LE Encrypted Client Test are no longer available in Bluetooth LE Secure Client tests
Signed-off-by: KETATNI Hassen <hassen.ketatni@sagemcom.com>
Change-Id: I96665587092ac16a401b3474159b1d5a047d1d21
|
|
|
|
|
|
Adding module SystemApi to SubscriptionManager functions
used by Bluetooth to add SUBSCRIPTION_TYPE_REMOTE_SIM.
Added corresponding cts tests to check that subscription
has been added and that it requires the right permissions.
Tag: #feature
Bug: 190441152
Test: atest android.telephony.cts.SubscriptionManagerTest
Change-Id: I079c2faffb49a51e205d60d59a08e397699dddb2
|
|
|
|
Bug: 197127958
Test: atest CtsHiddenApiBlocklistTestApiTestCases CtsHiddenApiBlocklistDebugClassTestCases
Change-Id: I47c454844af8b4797a518a810b17cd4fae49b03b
|
|
Pass criteria has been further relaxed for older devices.
Operating rate tests are disabled for devices launched on Android P
and below.
Also operating rate scaling factor is limited to
> 0 and <= 1.25 for devices launched on Android Q and below.
Bug: 184576106
Test: atest android.video.cts.CodecEncoderPerformanceTest
Test: atest android.video.cts.CodecDecoderPerformanceTest
Change-Id: Ifb19c206297ca29bffe07498e15a5196b32a3635
|
|
VP8 is no longer required to be tested for concurrency requirements
in media performance class tests
Bug: 197548945
Test: atest android.mediapc.cts
Change-Id: Idc467c546aa4fd4b09bdfd8ce49d5681f75d5f98
|
|
|
|
AccessibilityGestureDispatchTest#testClickWhenMagnified_matchesActualTouch CTS test for foldable devices.
The test was using the center of the screen to test the magnification function assuming that the point coincides with the center of the test activity. This is not true on foldable devices which can have the activity on one screen.
Solution: Instead of using the center of the screen, we used the center of the activity for the magnification function to capture click events.
Bug: https://partnerissuetracker.corp.google.com/u/2/issues/186542902
Test: cts-tradefed run commandAndExit cts -m CtsAccessibilityServiceTestCases -t android.accessibilityservice.cts.AccessibilityGestureDispatchTest#testClickWhenMagnified_matchesActualTouch
Verified on: Pixel 4 & development device
Change-Id: I8c1acd8a5d04e06ae8017a11289a0c9f619cada1
(cherry picked from commit 125b2e319a8e4b5b441b4a24d45a2829438d4621)
|