Age | Commit message (Collapse) | Author |
|
Flag: EXEMPT bugfix
Relnote: N/A
Bug: 406669065
LOW_COVERAGE_REASON=TEST_ONLY
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d3ad15d24fdaf24f502665837d0240c6619849c3)
Merged-In: I09bc9eede95cd5f48edb97d725225a2702456f2c
Change-Id: I09bc9eede95cd5f48edb97d725225a2702456f2c
|
|
Bug: 315320090
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:6e7b482edcc9716c952deab66eff65643ee319f8)
Merged-In: I07a253baaaf2a7c88b7027e9a44429a5419a9924
Change-Id: I07a253baaaf2a7c88b7027e9a44429a5419a9924
|
|
Due to the WRITE_MEDIA_IMAGES app op, photos access cannot actually be
denied. Since the role is fixed, the permission effectively is, too
Bug: 315320090
Test: atest MediaPermissionTest#testGalleryAppListedAsFixed
Flag: EXEMPT see bug
Relnote: none
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:17f747d7ea2e2bb9ac5bbb7654bd5354eb4632d0)
Merged-In: If9ae5366fe80fcd9eaf9c45dcee13e163207fbbe
Change-Id: If9ae5366fe80fcd9eaf9c45dcee13e163207fbbe
|
|
For targetSdk<23 apps, split permissions will go throught a review process when app upgrades. For now this will trigger HealthFitness revoke read heart rate permission alongside body sensors permission.
To mitigate the issue we disable this test for now as the impact is only limited to uncommon use cases.
Flag: EXEMPT bugfix
Relnote: N/A
Bug: 406669065
LOW_COVERAGE_REASON=TEST_ONLY
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4c7ef606a14ea5f111ab72ba0f7c27f5e2bfbd86)
Merged-In: Icd5955d09ee52e1d3222976288f5281ee3ebd0a4
Change-Id: Icd5955d09ee52e1d3222976288f5281ee3ebd0a4
|
|
This is being removed, due to unidentified crashed. Ensures the incall
test doesn't run on HSUM builds.
Bug: 408470449
Test: atest EnhancedConfirmationInCallTest
Flag: EXEMPT critical crash fix
Relnote: None
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:671bad75d3c80c9ac73b767b3e06f71c29ce8f86)
Merged-In: I38253e0cdae80fb9116e38926af81c642cbbd144
Change-Id: I38253e0cdae80fb9116e38926af81c642cbbd144
|
|
ag/31382100 (which adds the CREATE_VIRTUAL_DEVICE permission to the com.android.shell package) isn't there in Android 15, but its there in Android 16. So, AppPermissionsTest fails on 25Q1 builds, as it relies on shell for the above permission. So, we annotate the test to run on Android 16+, similar to DeviceAwarePermissionGrantTest.
Relnote: Annotate AppPermissionsTest to run on Android 16 and above
Test: atest AppPermissionsTest
Fixes: 406924219
LOW_COVERAGE_REASON=TEST_ONLY
Flag: EXEMPT test fix
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:eeae3f36407bd8cac7d69eeaa64cad939215902f)
Merged-In: I5ff1a33d146112c048a18adbbe2753b76d55078f
Change-Id: I5ff1a33d146112c048a18adbbe2753b76d55078f
|
|
|
|
Missing the future assignment in BaseUsePermissionTest
LOW_COVERAGE_REASON=TEST_ONLY
Bug: 403393912
Test: BaseUsePermissionTest
Flag: EXEMPT bugfix
Relnote: N/A
Change-Id: I0c60c8b36425b2b620a43585b452d4d925828a72
|
|
|
|
Bug: 403769622
Test: CtsPermissionTestCases:android.permission.cts.NoSystemFunctionPermissionTest#testSendSms
Flag: TEST_ONLY
Relnote: N/A
Change-Id: I4efbfd6fea5f37db26e323245fe70a2e3e532944
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/3541922
Change-Id: Ibc1586ee9593434cfc3f1a5b0b8d3574579e160f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
The method setMaxBound in
cts/tests/framework/base/windowmanager/util/src/android/server/wm/ProtoExtractors.java
is only available in S+. Hence fallback to the original behavior for R-
to avoid test failures
LOW_COVERAGE_REASON=TEST_ONLY
Test: BaseUsePermissionTest
Flag: EXEMPT bugfix
Fixes: 403393912
Relnote: N/A
Change-Id: I10170dd9e563705b1e27e3fa95c0d0b31e6e63c7
|
|
|
|
Link fix for BaseUsePermissionTest
LOW_COVERAGE_REASON=TEST_ONLY
Test: BaseUsePermissionTest
Flag: EXEMPT bugfix
Fixes: 403393912
Relnote: N/A
Change-Id: Ia0222e271401a8bc7300a96ab7c1cbe40e81dfc8
|
|
VDM tests don't work on A15 + mainline without ag/31410712
Also cleaning up the flags launched in A15.
Bug: 402857630
Test: atest
Flag: EXEMPT test improvement
LOW_COVERAGE_REASON=TEST_ONLY
Relnote: n/a
Change-Id: I1768abc83d362817a8c2fc581d2ba9ff73c7e7e9
|
|
Bug: 368633836
Test: presubmit
Relnote: n/a
LOW_COVERAGE_REASON=NON_CODE_ONLY
Flag: android.companion.virtualdevice.flags.enable_limited_vdm_role
Change-Id: I4f71eccabf3b746767d70092cdf3591d944efe20
|
|
LOW_COVERAGE_REASON=NON_CODE_ONLY" into main
|
|
LOW_COVERAGE_REASON=NON_CODE_ONLY
Bug: 364416355
Change-Id: Id69901a74d86e4972df0ccbcb54903795a6e851d
Flag: android.xr.xr_manifest_entries
Test: Checked that project still built.
Relnote: None
|
|
test item will turn on the private space mode, and this mode turns on a
large number of app operations and multiuser operations, it will be
easier for low-end devices to run in complete.
Add test waitForIdle(timeout) to make sure time execute finish.
Bug: 403200469
Test: android.app.role.cts.RoleManagerTest
#openDefaultAppListAndSetDefaultAppThenIsDefaultAppForPrivateSpace
Change-Id: I107c5a3e2c9e3fce6f68e6cefba0c6133bd547d0
|
|
|
|
b/398830041 currently impacts flag value matching for mainline module on
V platform. According to trunk stable team, these flag checks can be
replaced with sdk version check. Hence removing the flag checks in this
CL
Bug: 396234389
Test: Build
Flag: EXEMPT bugfix
Relnote: N/A
Change-Id: Id351f1516d9db763e8d765da552d4da2182300b9
|
|
- Fix GrantPermissionsActivity for non-device-aware permissions.
Such requests should not be ignored, but should fallback to the
default device.
- Fix the permission check for passing grant results. When requesting
default device aware permission from virtual device, the call to
checkPermission uses the wrong context. It can simply use
mPackageManager, which is always associated with the target device.
Fix: 401540899
Test: atest
Relnote: n/a
Flag: EXEMPT bugfix
Change-Id: Ib5de5ce0cf09f6ad1e445b01ca2443bf102ab598
|
|
into main
|
|
Fixes: 400512397
Test: atest SafetyCenterFunctionalTestCases and treehugger
Flag: EXEMPT test only change
Relnote: N/a
LOW_COVERAGE_REASON=b/360423897
Change-Id: I1491376b01562927e183fd31f4eb83f40d9200be
|
|
|
|
This adds "assume"s to two tests:
- removeSmsRoleHolderThenPermissionIsRevoked
- requestRoleThenBlockRequestRoleDialogByRestrictedSettingDialog
...which will cause the tests to end with "ASSUMPTION_FAILED" in the
case that the device has no default SMS app when the test starts. This
scenario currently happens on GSI builds, showing up as a failed test.
This also adds "assume"s to:
- openDefaultAppListThenIsNotDefaultAppInList
...which has a flaw that occurs when the installer test helper app takes
on any default app roles automatically, which may occur if the role has
no holder when the test starts.
Fix: 365796249
Test: atest RoleManagerTest
Flag: TEST_ONLY
Relnote: N/A
LOW_COVERAGE_REASON=TEST_ONLY
Change-Id: Ia5355189e026cd1fd9bc8a10a2b34dfb63c6cfe8
|
|
|
|
UI logs will help visualizing the current
screen in foreground when timeout occur.
Bug: 400595465
Test: build
Flag: EXEMPT test fix
Relnote: test fix
LOW_COVERAGE_REASON=TEST_ONLY
Change-Id: Id1e3a4f4cc3d4e522aa7a69c32193310e03dfdee
|
|
grant/deny click"" into main
|
|
This reverts commit 8fde9e1a4477a795ce5ff276b1163d6fc2dd3140.
Reason for revert: b/400595465
Change-Id: I86832ebb4e2e6530630779135f41f198271f3a89
|
|
click" into main
|
|
proceeding"" into main
|
|
|
|
Android 16 introduces a new restriction that only allowlisted
DeviceConfig flags can be modified by the shell user. The
camera_mic_icons_enabled flag is not on the allowlist since it
was only intended to be used during the initial feature development
and should be enabled by default. This commit updates the test
that currently modifies this flag to only verify that the flag
is enabled.
Bug: 390242290
Flag: android.security.protect_device_config_flags
Relnote: N/A
Test: atest CtsPermissionUiTestCases:CameraMicIndicatorsPermissionTest
Change-Id: I11ed9c3b6c29a32557add30c5894e728ca9712f7
LOW_COVERAGE_REASON=TEST_ONLY
|
|
|
|
This reverts commit 9dc20037e386ce043da72a9e49405accf50649ca.
Reason for revert: re-landing after adding try/catch
Change-Id: Id0ca88026cb94a7021c0dc71f30f51ca82d01bc6
LOW_COVERAGE_REASON=TEST_ONLY
|
|
enabled." into main
|
|
This reverts commit 9446bac763eaa0855629605d5e2b9fb34bd144e7.
Reason for revert: DroidMonitor: Potential culprit for http://b/399895919 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Change-Id: I9531c7f0be6c933a323b28726e669b37cee0704b
|
|
The usage of waitForWindowTransition is flaky imo,
waitForWindowTransition waits for TYPE_WINDOW_STATE_CHANGED
and TYPE_WINDOW_CONTENT_CHANGED a11y events. These events
could be generated by any activity/window. The
problem lies within UiAutomation where these events
might not be captured due to flipping of boolean flag
to false prematurely on older platforms, which causes
UiAutomation to stop capturing these events. it was
fixed in ag/31361450 but can't be backported.
Also, waitForWindowTransition doesn't necessarily waits
for window transition triggered by
GrantPermissionsActivity, it can be triggered by
StartForFutureActivity or RequestPermissionActivity.
So, theoritically it may give false positive results.
The new code verifies that after making
request permission call, we see a valid activity
state for GrantPermissionsActivity before
proceeding. This seems more robust to me.
Bug: 396788297
Test: atest CtsPermissionUiTestCases --iterations 5
Flag: EXEMPT test fix
Relnote: test fix
LOW_COVERAGE_REASON=TEST_ONLY
Change-Id: I1a9642272f7ece47329e5bb41e799a3fdcb9f0e4
|
|
The test doesn't need to wait for (flaky) window transition
event after grant/deny button click in permission dailog.
The test waits for onRequestPermissionsResult callback
before asserting permission states, and that is good
enough. So, imo we doesn't need unnecessary window
transition assertion.
Bug: 396788297
Test: atest LocationAccuracyTest --iterations 10
Flag: EXEMPT test fix
Relnote: test fix
LOW_COVERAGE_REASON=TEST_ONLY
Change-Id: I532b51e0c76a33255f1a9bcca4ca6c39faedbe63
|
|
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/3512231
Change-Id: Iee8a47b6baa96a295db31f7c8cbce8ce475578ce
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
permission test" into main
|
|
permission test
Bug: 396422648
Test: atest android.permission.cts.DevicePermissionsTest
Flag: EXEMPT bug fix
RelNote: N/A
Change-Id: I98f73d4a1128787b5daa63248536949e1330f8c7
LOW_COVERAGE_REASON=TEST_ONLY
|
|
|
|
|
|
BodySensor is not supported on automotive.
Bug:388943834
Test: atest android.permissionui.cts.PermissionSplitTest
LOW_COVERAGE_REASON=TEST_ONLY
Flag: TEST_ONLY
Relnote: skip CTS test for BODY_SENSORS for automotive
Change-Id: I3ce44730fefeafea952720d3534b31a66afd9e64
|
|
If the activity is already present, a transition will not occur when
launching the activity unless it's cleared first.
Bug: 397102024
Test: atest android.permissionui.cts.PermissionDecisionsTest
Flag: TEST_ONLY
Relnote: Fix permission decisions CTS test when activity already showing
LOW_COVERAGE_REASON=TEST_ONLY
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:90408f6fdc7c5564a933b2beafde71df319f02a8)
Merged-In: I3f08f39497a9f9bfce5b049eaad4749febc22f9f
Change-Id: I3f08f39497a9f9bfce5b049eaad4749febc22f9f
|
|
|