| d405431bc97087184d1ecb77e4fa495a6ca4709a |
|
24-Jun-2016 |
Chris Wren <cwren@android.com> |
use an observer for the default sound
matches other settings use, and also improves testability of buzzbeepblink
Change-Id: I9445448c4c4f24f4f49f7cb1fdcd2f5362944606
/frameworks/base/services/tests/servicestests/src/com/android/internal/util/FakeSettingsProviderTest.java
|
| 3394a8e52393b71d757766047ce05fe7813a8e82 |
|
23-Jun-2016 |
Guang Zhu <guangzhu@google.com> |
temporarily disable FakeSettingsProviderTest
Bug: 29281167
Change-Id: I463d7707c197bd114de762c86e3b3e574d456e3b
/frameworks/base/services/tests/servicestests/src/com/android/internal/util/FakeSettingsProviderTest.java
|
| 6d553f6dfdcc188fa6b17d4abb11d6222009a8fb |
|
04-Jun-2016 |
Lorenzo Colitti <lorenzo@google.com> |
Add a FakeSettingsProvider and use it in ConnectivityServiceTest.
This class makes it easier to test code that uses Settings:
1. Real device or emulator settings don't affect the code under
test; all settings always start off empty.
2. It's possible to change settings from the test without
affecting system settings.
3. No changes are needed to the code under test. The changes to
the tests are simple: just add a fake ContentResolver to
whatever mock Context is already used by the test, and make
that ContentResolver use the fake provider.
Bug: 23113288
Change-Id: I5e7e5a87571444ae49ccf551705620675a36cd17
/frameworks/base/services/tests/servicestests/src/com/android/internal/util/FakeSettingsProviderTest.java
|