Bug: 32849428
* goog/cw-f-dev: (122 commits)
Fixed CTS unit tests
Fixing layout of several test suites for round screens.
Fix test case context which is not fully visible on wear.
Fix build for nyc-dr1-dev
Check that H.264 is available before checking max frame rate
DO NOT MERGE: Bump CTS and CTS Verifier to 5.1_r14
DO NOT MERGE: Bump CTS and CTS Verifier to 6.0_r13
Run DynamicConfig setup twice
DO NOT MERGE: Bump CTS and CTS Verifier to 7.0_r4
Fix UserRestrictionsTest.testUserRestrictions_secondaryProfileOwnerOnly
Generate and include checksum data with CTS report submissions Test: Used exploratory tests and unit tests in ChecksumReporterTest.java to verify the behavior. * All TestResults are added from an InvocationResult * Able to verify TestResult against previously calculated checksum * CRCs are created for all files in a directory including subdirectories * Checksum integrity is maintained while serializing to/from disk * When possible checksum data is compressed before report submission
Add retry logic for adoptable storage tests
Catch case where browser is protected by a permission
Fix failure due to accessibility node not updated after scrolling.
Fix DO/PO Wifi CTS
Test: Fix testFindAll result listener not set issue
Updating CTS Security patch to 2017-01
DO NOT MERGE ANYWHERE: bump cts for 201701 security public bulletin
DO NOT MERGE ANYWHERE: bump cts for 201701 security public bulletin
CTS Test for security vulnerability fix: Effect command might allow negative indexes
...
Change-Id: I07b3bb0249eebcae5760d08c98cdde1ac5b01601
Certain tests interacting with device idle
must set correctly both the normal and wear
device idle setting space.
Bug: 32183373
Test: Run on wear device and Nexus6P
run cts --skip-device-info -m CtsHostsideNetworkTests -t com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDozeModeMetered_enabledButWhitelistedOnNotificationAction
run cts --skip-device-info -m CtsHostsideNetworkTests -t com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDozeModeNonMetered_enabledButWhitelistedOnNotificationAction
Change-Id: I6a53d29021a7d4a257b102a4d3bd5d2cc845c16f
(cherry picked from commit a84bb771d1)
Certain tests interacting with device idle
must set correctly both the normal and wear
device idle setting space.
Bug: 32183373
Test: Run on wear device and Nexus6P
run cts --skip-device-info -m CtsHostsideNetworkTests -t com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDozeModeMetered_enabledButWhitelistedOnNotificationAction
run cts --skip-device-info -m CtsHostsideNetworkTests -t com.android.cts.net.HostsideRestrictBackgroundNetworkTests#testDozeModeNonMetered_enabledButWhitelistedOnNotificationAction
Change-Id: I6a53d29021a7d4a257b102a4d3bd5d2cc845c16f
Ensure that password is not output in toString() for an enterprise
credential.
Bug: 25624963
Test: Run this CTS test: run cts --module CtsNetTestCases --test android.net.wifi.cts.WifiEnterpriseConfigTest#testEnterpriseConfigDoesNotPrintPassword
Change-Id: I84a62ae5d37aa7d397203f41362dadb8ceba1e62
Symptom: It should be more reasonable to control battery saver function from setting DB instead of plugging/unplugging charger for “CtsHostsideNetworkTests” test case.
Root Cause: The test function “setBatterySaverMode” of “CtsHostsideNetworkTests” use command to set setting DB when trying to turn on battery saver. But while trying to turn off battery saver, it only use charger plug-in event. It should be more reasonable to turn off battery saver through similar DB setting as this function did at turning on.
Solution: To control battery saver function from setting DB.
Project:
Note:
Test done by RD:
Futher testing need Q team's support:
Bug: 31897608
Change-Id: Id70ba458e85f98393d7652bb4e79bd182172c60f
