• Home
  • History
  • Annotate
  • only in /libcore/harmony-tests/src/test/java/org/apache/harmony/tests/java/util/prefs/
History log of /libcore/harmony-tests/src/test/java/org/apache/harmony/tests/java/util/prefs/
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
e34fbfb66a724284a9722892fa8f51f7c663ed86 13-Jun-2016 Przemyslaw Szczepaniak <pszczepaniak@google.com> Fix Preferences regression.

This change fixes reading filesystem-saved
java.util.prefs.Preferences.

Due to a bug in XmlSupport, when reading the
filesystem-saved preferences, the reader was
throwing an exception. The Android
implementation of xml parser adds additional
nodes that were not Elements, this was
causing a cast exception (the old code was expecting
only Elements).

FileSystemPreferences class was swallowing exceptions if
they happen during preferences content reading.
This changes adds additional logging to prevent this.

Bug: 27645233
Change-Id: Ieebd8a6a1002111654005bfcc42009b01c89ea70
(cherry picked from commit 44d29b0a9012a66f5db5a8130017568a55c11668)
referencesTest.java
96b40e87c32023084d7153360b1fa0c44c598095 12-Aug-2015 Narayan Kamath <narayan@google.com> Stop using libcore's java.util.prefs implementation.

Change-Id: If30217f18b124871ff43a39b0fb7a55bd06f095b
bstractPreferencesTest.java
referencesTest.java
9252ce2bef667745ad23601d5ac25b435e6e77f5 17-Sep-2014 Neil Fuller <nfuller@google.com> Fix FilePreferencesImplTest test initialization errors.

Fix IllegalAccessException from Preferences when this
test is run "stand alone".

The java.util.prefs.Preferences class is normally already
initialized by the time this test runs (and initialized
when there is no system property). However, in
standalone cases the system property is pointing to a
class that cannot be instantiated by ServiceLoader.

The normal fallback process when the system property is
not set would lead to FilePreferencesFactoryImpl being
instantiated directly by java.util.prefs.Preferences,
which is legal.

Removing the system property fixes the issue. The
FilePreferencesFactoryImpl is not intended to be created
by ServiceLoader and so it is reasonable that the class
is declared as package-protected. This test is for
the implementation so it's reasonable just to bypass
Preferences entirely.

Bug: 17515057

(cherry picked from commit 95c68ff724f7cf1afc2970b0d25e108e580307ed)

Change-Id: Ia860e299983b7b87753fe1dc0259b0d4ea2477f3
ilePreferencesImplTest.java
b0b81dfb681cf401b3fc108b9abe432ee6736164 22-Aug-2014 Narayan Kamath <narayan@google.com> Move preference tests over from external/apache-harmony.

Also fixes all remaining failures. Most of them were
due to us not setting "user.dir" and "user.home" correctly.
Android has traditionally left those values blank. To fix
these tests, we need to change the default prefs factory
to one rooted at a temporary directory.

Note that this change attempts the minimal possible cleanup
(mainly style, commented code formatting etc.) to these files.

bug: 13881847

(cherry picked from commit a152f62d4d81ef6500b3e02dbc381e2414f9a11f)

Change-Id: Ie32a61e1b911dcd317c688f86e487f9ea778b31f
bstractPreferencesTest.java
ackingStoreExceptionTest.java
ilePreferencesImplTest.java
nvalidPreferencesFormatExceptionTest.java
ockAbstractPreferences.java
ockPreferencesFactory.java
odeChangeEventTest.java
odeChangeListenerTest.java
referenceChangeEventTest.java
referenceChangeListenerTest.java
referencesFactoryTest.java
referencesTest.java