Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix DozeConfigurationTest

Browse Source 
Settings.Secure.putString() was failing to remove the setting for
config_dozeAlwaysOnEnabled, so the test would only pass if the default
setting matched what was currently set on the device.

The fix seems to be to use
Settings.Secure.putStringForUser(UserHandle.USER_CURRENT), because
systemui tests are now running as the system

Test: atest com.android.systemui.doze.DozeConfigurationTest#alwaysOn_followsConfigByDefault
Change-Id: I482e1b72b4a3567d5448ded0aa110f2e3e05c515
This commit is contained in:
Evan Laird
2018-10-05 13:16:50 -04:00
parent aeeb3f5eda
commit 8a1707e021
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/SystemUI/tests/src/com/android/systemui/doze/DozeConfigurationTest.java
View File

@@ -47,10 +47,10 @@ public class DozeConfigurationTest extends SysuiTestCase {
return;
}
Settings.Secure.putString(mContext.getContentResolver(), Settings.Secure.DOZE_ALWAYS_ON,
null);
Settings.Secure.putStringForUser(mContext.getContentResolver(),
Settings.Secure.DOZE_ALWAYS_ON, null, UserHandle.USER_CURRENT);
boolean defaultValue = mContext.getResources()
.getBoolean(com.android.internal.R.bool.config_dozeAlwaysOnEnabled);
assertEquals(mDozeConfig.alwaysOnEnabled(UserHandle.USER_CURRENT), defaultValue);
assertEquals(defaultValue, mDozeConfig.alwaysOnEnabled(UserHandle.USER_CURRENT));
}
}