commit 361d626f6acab5bb9f48cefc88a9118eaa986939
author Unsuk Jung <unsuk@google.com> Fri Sep 19 04:38:24 2014 -0700
committer Unsuk Jung <unsuk@google.com> Fri Sep 19 11:46:08 2014 +0000
tree 89b1ee0831910e63bb597b300bd0960f14e45fbc
parent e17adc3dc0e61951fbf815c3d02dc6bf48767d1b

DO NOT MERGE A few tests in DevicePolicyManagerTests added to knownfailures.

A few tests in DevicePoliyManagerTests, did caused the security settings to change to lock-screen (with an empty password) or the swipe-to-unlock impacting all subsequent CTS tests. Addding to knownfailures so that we can keep running other tests while debugging the problem.

Bug: 17496766
Change-Id: Ie6ef946a04a36ae6b0b4393e582553900641f272

tests/expectations/knownfailures.txt

diff --git a/tests/expectations/knownfailures.txt b/tests/expectations/knownfailures.txt
index 706a663..3802c73 100644
--- a/tests/expectations/knownfailures.txt
+++ b/tests/expectations/knownfailures.txt
@@ -69,5 +69,16 @@
     "android.hardware.camera2.cts.AllocationTest#testParamSensitivity"
   ],
   bug: 17530117
+},
+{
+  description: "these tests locks the screen with an emtpy password or swipe-to-unlock, blocking subsequent test to dismiss keyguard",
+  names: [
+    "android.admin.cts.DevicePolicyManagerTest#testPasswordQuality_something",
+    "android.admin.cts.DevicePolicyManagerTest#testPasswordQuality_numeric",
+    "android.admin.cts.DevicePolicyManagerTest#testPasswordQuality_alphabetic",
+    "android.admin.cts.DevicePolicyManagerTest#testPasswordQuality_alphanumeric",
+    "android.admin.cts.DevicePolicyManagerTest#testGetMaximumFailedPasswordsForWipe"
+  ],
+  bug: 17496766
 }
 ]