| 8157bc86afeb76f2391741491917f90003aa2569 |
|
13-May-2015 |
Nicolas Geoffray <ngeoffray@google.com> |
Refactor the test to ensure positive tests do pass.
Change-Id: Idcfb97fdc6c2043ee904d0e53f1bfb58bb6ddb96
|
| f6a432f7f98dabbc51a062c4bda33b706330e91d |
|
21-May-2014 |
Neil Fuller <nfuller@google.com> |
Keep Preferences tests working
Apply changes made as part of I6019441c65b398376d84264f1e4c9776507533eb
more widely.
Bug: 15105787
Change-Id: I2e44487b1561dd564bfa41d65995a61091b011eb
|
| eac95336d177366b2f2da2110db39abbc49f524a |
|
17-Feb-2014 |
Narayan Kamath <narayan@google.com> |
DO NOT MERGE Fix Preferences related tests, document limitations.
- The default Preferences factory methods are entirely
useless on android. "java.home" points to a location
in a read-only partition and "user.home" is set to "/"
which apps are not allowed to write to. A strong warning
has been added against these methods.
- We continue to support the underlying default preferences
implementation (even though there's no way to use the impl.
directly except by reflection) to help apps transition *just
in case* they were manually massing "user.home" and "java.home".
- Add a fake preferences factory that allows us to
use a new (temporary) preferences root for every test.
Fixed a test interdependency issue that was uncovered
by this change.
(cherry picked from commit b27fd46c694f8ee4118d6b9bdd61741472ee92b5)
Bug: 13763685
Bug: 13763900
Change-Id: I6019441c65b398376d84264f1e4c9776507533eb
|
| b27fd46c694f8ee4118d6b9bdd61741472ee92b5 |
|
17-Feb-2014 |
Narayan Kamath <narayan@google.com> |
Fix Preferences related tests, document limitations.
- The default Preferences factory methods are entirely
useless on android. "java.home" points to a location
in a read-only partition and "user.home" is set to "/"
which apps are not allowed to write to. A strong warning
has been added against these methods.
- We continue to support the underlying default preferences
implementation (even though there's no way to use the impl.
directly except by reflection) to help apps transition *just
in case* they were manually massing "user.home" and "java.home".
- Add a fake preferences factory that allows us to
use a new (temporary) preferences root for every test.
Fixed a test interdependency issue that was uncovered
by this change.
Change-Id: I6019441c65b398376d84264f1e4c9776507533eb
|
| c3002fbb233734d150a2fcef30fac69260c9ac6e |
|
15-Aug-2011 |
Jesse Wilson <jessewilson@google.com> |
Make OldAbstractPreferencesTest resistent to a dirty environment.
The CTS test harness doesn't sanitize the preferences between tests
so we need to make sure it's clean in the test.
Change-Id: Idc80ac23f97431d31c902ad6a985ee8010a008f8
|
| f296f0cb984fb2435bedad23439c1fdc2ad61bd0 |
|
15-Aug-2011 |
Jesse Wilson <jessewilson@google.com> |
Fix a racy preferences test to not rely on disk flush latency.
This test invisibly uses two threads - the test thread and the
preference API's preference change thread. This test was relying
on flush() taking long enough that the other thread would have
posted its event before it returned.
The new test just waits up to 100ms. This is still racy but it
eliminated the false failures in my runs.
Change-Id: I87799b36cb4e5e26d8ca04e4529d1db0b936acb3
|
| 80c9f71990a6655b7b2b43dc1946487e917f0f9d |
|
09-Dec-2010 |
Jesse Wilson <jessewilson@google.com> |
Remove prefs tests duplicated with Harmony.
We have at least one expectation set (on PreferencesTest.testImportPreferences)
where the expectation is different on Harmony than on our revised copy.
Change-Id: I9c983755a91728d2f6bdee7ec59439c10e327cda
http://b/3246523
|