| 23cbe85610f780134cc77dd4a54732a22ed6e86e |
18-May-2016 |
Yohei Yukawa <yukawa@google.com> |
Move LocaleList to avoid layering violation.
Since LocaleList needs to depend on android.os.Parcelable, we cannot let
that class belong to "android.util" package, which causes layering
violation.
Bug: 28819696
Change-Id: Ia8de2ee9df3dd0a42b1fe84574439519b680fe18
ocaleListTest.java
|
| f90177629a5b69ca3a80466c0ab55abfeb6d26b2 |
01-Aug-2015 |
Abodunrinwa Toki <toki@google.com> |
Turn off failing tests in FrameworksCoreTests.
We want a green state so we can confidence in tests we write
going forward.
Change-Id: I2c8db848897b56d0c64202ad28861eb4a7572e07
essageQueueTest.java
raceTest.java
torage/StorageManagerIntegrationTest.java
|
| 4f5e8b3ca489245005b76176ac6d28f5f184f3fe |
12-Jun-2015 |
Jeff Sharkey <jsharkey@android.com> |
Valid filenames have length limits!
ext4 filenames are at most 255 bytes. vfat filenames are bit more
lax, but we're often saving them on ext4 through a FUSE daemon, so
limit them the same way.
Since package names are used as directory names, verify that they're
valid filenames.
Tests to verify behavior.
Bug: 18689171
Change-Id: If7df4c40d352954510b71de4ff05d78259c721ed
ileUtilsTest.java
|
| 62539a220c6810f66b63060326bd1668f7d6b029 |
23-Apr-2015 |
Ben Kwa <kenobi@google.com> |
Move extension checking code into FileUtils.
Move code for checking file extensions and MIME types from
ExternalStorageProvider into android.os.FileUtils, so it can be used by
other clients (e.g. DownloadsProvider).
BUG=20157955
Change-Id: Ib16a16af723c21fb8d2912c8917dfd68653ea6fa
ileUtilsTest.java
|
| 9962ed55759336642cfaba27e8b2a47822f562fe |
18-Dec-2014 |
Elliott Hughes <enh@google.com> |
am 93241de7: Merge "Remove a bitrotted test."
automerge: ba6982a
* commit 'ba6982a16cb3b9f6196fdac11d1d90a02eb32cfd':
Remove a bitrotted test.
|
| 988fd73499492d5826754ca85acac1e64357121c |
18-Dec-2014 |
Elliott Hughes <enh@google.com> |
Remove a bitrotted test.
Change-Id: I4c44f2da0544dbfde8e340f7f477191725c5fb8b
ELinuxTest.java
|
| 0cce5355b45d835f95a8918b8b803fd977d374e4 |
26-Nov-2014 |
Jeff Sharkey <jsharkey@android.com> |
Sanitize display names, keep extensions intact.
When creating or renaming files on external storage, sanitize the
requested display names to be valid FAT filenames. This also fixes
a handful of directory traversal bugs.
Also relax logic around generating display names to allow any
extension which maps to the requested MIME type. Tests to verify.
Bug: 18512473, 18504132
Change-Id: I89e632019ee145f53d9d9d2050932f8939a756af
ileUtilsTest.java
|
| 941a8ba1a6043cf84a7bf622e44a0b4f7abd0178 |
21-Aug-2014 |
Jeff Sharkey <jsharkey@android.com> |
Installing splits into ASECs!
Sessions can now zero-copy data directly into pre-allocated ASEC
containers. Then at commit time, we compute the total size of the
final app, including any inherited APKs and unpacked libraries, and
resize the container in one step.
This supports both brand new ASEC installs and inheriting from
existing ASEC installs. To keep things simple, it currently requires
copying any inherited ASEC contents, but this could be optimized in
the future.
Expose new vold resize command, and allow read-write mounting of ASEC
containers. Move native library extraction into the installer flow,
since it needs to happen before ASEC is sealed. Move multiArch flag
into NativeLibraryHelper, instead of making everyone pass it
around. Migrate size calculation to shared location.
Separate "other" package name in public API, provide a path to a
storage device when relevant, and add more docs.
Bug: 16514385
Change-Id: I06c6ce588d312ee7e64cce02733895d640b88456
torage/AsecTests.java
|
| 78cc340c2de873d6995c283b777476f7237d690f |
22-May-2014 |
Jeff Sharkey <jsharkey@android.com> |
Offer to stream and fsync() install sessions.
Installers are interested in both streaming APK data and establishing
a happens-after relationship to support resuming downloads after a
process kill or battery pull.
This exposes a generic OutputStream for writing, and hooks up flush()
to be a blocking call which returns only when all outstanding write()
data has been fsync()'ed to disk.
Tests to verify behavior.
Bug: 14975160
Change-Id: I38289867c80ac659163bb0c2158ef12d99cc570d
ileBridgeTest.java
|
| ebf8ad5d91b22eb4359c75711a5b70ddcce0723d |
31-Jan-2014 |
Jeff Sharkey <jsharkey@android.com> |
Update DrmOutputStream to use raw FileDescriptor.
This allows DownloadManager to use FDs, paving the way for downloading
directly to content:// Uris.
Also return flag indicating if deleteOlderFiles() actually deleted
anything. Update tests to verify.
Bug: 5287571
Change-Id: I2579e5e2113f31b2860d7b021bd61c91b6310963
ileUtilsTest.java
|
| 4ca728c064aeab644f6d044e0285eaa056818b8a |
11-Jan-2014 |
Jeff Sharkey <jsharkey@android.com> |
Detect removable and emulated secondary storage.
Also rename existing secondary storage API to match naming
convention in rest of class.
Bug: 11536709
Change-Id: I2684c817de4982b414893d2d9927a21e3f171d53
ileUtilsTest.java
|
| d9526907d1a51ef0b35bfbbeee43fa209d8b5bbf |
14-Mar-2013 |
Jeff Sharkey <jsharkey@android.com> |
Move deleteOlderFiles() to framework, tests.
Supports both age and count based constraints. Added light docs and
tests to verify behavior.
Bug: 8387555
Change-Id: If4d0dac8bc54ce705c2a339bc09a60ea748728b8
ileUtilsTest.java
|
| 58ed5d748c0b9b64845975ef5844ad313de7c3f6 |
07-Nov-2012 |
Kenny Root <kroot@google.com> |
am 768d9e1a: Merge "Correct executable bit for source files"
* commit '768d9e1a72ceee7d4a5f608776b87b62d6ce4a04':
Correct executable bit for source files
|
| 3a084af2e90849aaa8beb3a610189e3399c63ea0 |
07-Nov-2012 |
Kenny Root <kroot@google.com> |
Correct executable bit for source files
Many media files and source code files were marked as executable in Git.
Remove those.
Also a shell script and python script were not marked as executable.
Change-Id: Ieb51bafb46c895a21d2e83696f5a901ba752b2c5
torage/AsecTests.java
|
| 9a994b5350731b8169a9b25463f57266ee2988fb |
17-Aug-2012 |
Kenny Root <kroot@google.com> |
am 050c87f8: am a950daf5: Merge changes Ieb566a2a,I953057cd
* commit '050c87f87e2a48c7bc90f5b15fb6e4e37e667286':
Use Libcore's stat instead of FileUtils#getFileStatus
Use Libcore.os.stat instead of FileUtils
|
| 98e15e78934a00cf46f2be55472b7fd7a39ac0de |
16-Aug-2012 |
Kenny Root <kroot@google.com> |
Use Libcore's stat instead of FileUtils#getFileStatus
Remove the last user of FileUtils#getFileStatus and move it to
Libcore.os.stat instead. Then we can remove the JNI code that does the
equivalent of a stat.
Change-Id: Ieb566a2a8a17c2dd0150724b4eb3ac1cc41c823d
ileUtilsTest.java
|
| f02b60aa4f367516f40cf3d60fffae0c6fe3e1b8 |
16-Aug-2012 |
Dianne Hackborn <hackbod@google.com> |
Rename UserId to UserHandle.
This is the start of turning this into a formal public API.
Change-Id: I5786d2c320f1de41a06ed5d0f65adb68967287a0
rocessTest.java
|
| 9630704ed3b265f008a8f64ec60a33cf9dcd3345 |
28-Jul-2012 |
Jeff Brown <jeffbrown@google.com> |
Power manager rewrite.
The major goal of this rewrite is to make it easier to implement
power management policies correctly. According, the new
implementation primarily uses state-based rather than event-based
triggers for applying changes to the current power state.
For example, when an application requests that the proximity
sensor be used to manage the screen state (by way of a wake lock),
the power manager makes note of the fact that the set of
wake locks changed. Then it executes a common update function
that recalculates the entire state, first looking at wake locks,
then considering user activity, and eventually determining whether
the screen should be turned on or off. At this point it may
make a request to a component called the DisplayPowerController
to asynchronously update the display's powe state. Likewise,
DisplayPowerController makes note of the updated power request
and schedules its own update function to figure out what needs
to be changed.
The big benefit of this approach is that it's easy to mutate
multiple properties of the power state simultaneously then
apply their joint effects together all at once. Transitions
between states are detected and resolved by the update in
a consistent manner.
The new power manager service has is implemented as a set of
loosely coupled components. For the most part, information
only flows one way through these components (by issuing a
request to that component) although some components support
sending a message back to indicate when the work has been
completed. For example, the DisplayPowerController posts
a callback runnable asynchronously to tell the PowerManagerService
when the display is ready. An important feature of this
approach is that each component neatly encapsulates its
state and maintains its own invariants. Moreover, we do
not need to worry about deadlocks or awkward mutual exclusion
semantics because most of the requests are asynchronous.
The benefits of this design are especially apparent in
the implementation of the screen on / off and brightness
control animations which are able to take advantage of
framework features like properties, ObjectAnimator
and Choreographer.
The screen on / off animation is now the responsibility
of the power manager (instead of surface flinger). This change
makes it much easier to ensure that the animation is properly
coordinated with other power state changes and eliminates
the cause of race conditions in the older implementation.
The because of the userActivity() function has been changed
so that it never wakes the device from sleep. This change
removes ambiguity around forcing or disabling user activity
for various purposes. To wake the device, use wakeUp().
To put it to sleep, use goToSleep(). Simple.
The power manager service interface and API has been significantly
simplified and consolidated. Also fixed some inconsistencies
related to how the minimum and maximum screen brightness setting
was presented in brightness control widgets and enforced behind
the scenes.
At present the following features are implemented:
- Wake locks.
- User activity.
- Wake up / go to sleep.
- Power state broadcasts.
- Battery stats and event log notifications.
- Dreams.
- Proximity screen off.
- Animated screen on / off transitions.
- Auto-dimming.
- Auto-brightness control for the screen backlight with
different timeouts for ramping up versus ramping down.
- Auto-on when plugged or unplugged.
- Stay on when plugged.
- Device administration maximum user activity timeout.
- Application controlled brightness via window manager.
The following features are not yet implemented:
- Reduced user activity timeout for the key guard.
- Reduced user activity timeout for the phone application.
- Coordinating screen on barriers with the window manager.
- Preventing auto-rotation during power state changes.
- Auto-brightness adjustment setting (feature was disabled
in previous version of the power manager service pending
an improved UI design so leaving it out for now).
- Interpolated brightness control (a proposed new scheme
for more compactly specifying auto-brightness levels
in config.xml).
- Button / keyboard backlight control.
- Change window manager to associated WorkSource with
KEEP_SCREEN_ON_FLAG wake lock instead of talking
directly to the battery stats service.
- Optionally support animating screen brightness when
turning on/off instead of playing electron beam animation
(config_animateScreenLights).
Change-Id: I1d7a52e98f0449f76d70bf421f6a7f245957d1d7
rightnessLimit.java
|
| dc09102c8dad2668ec8c1228fee8762aa81153a5 |
13-Aug-2012 |
Amith Yamasani <yamasani@google.com> |
Tests for mapping android name to uid
This tests some changes made to bionic.
Change-Id: I7ff8c7f94f6b4bfff64d4e15d4a1a3516a453180
rocessTest.java
|
| e38b1c4d156a569efc646e86a72ab3a3e3ccf6fc |
08-Jun-2012 |
Kenny Root <kroot@google.com> |
resolved conflicts for merge of 9855f6e2 to jb-dev-plus-aosp
Change-Id: I012bd3b5946dedba3439285caa93739d44ebc60f
|
| 6dceb88f1c7c42c6ab43834af2c993d599895d82 |
12-Apr-2012 |
Kenny Root <kroot@google.com> |
Allow forward locked apps to be in ASECs
We couldn't put forward-locked apps in ASEC containers before since we
didn't have any permissioned filesystems. This adds the ability for
forward-locked applications to be in ASEC containers.
This means that forward locked applications will be able to be on the SD
card now.
This change also removes the old type of forward-locking that placed
parts of apps in /data/app-private. Now all forward-locked applications
will be in ASEC containers.
Change-Id: I17ae0b0d65a4a965ef33c0ac2c47e990e55707ad
torage/AsecTests.java
|
| c07fca3831baf4d812dd724f506b4ed23dcc39e0 |
13-Jan-2012 |
Stephen Smalley <sds@tycho.nsa.gov> |
Add JNI bindings for some of the libselinux interfaces.
Change-Id: Ifcc68cb06f9f56a04f3bc64dd9906a9436fabc88
ELinuxTest.java
|
| 13c7197da8a16f77f6398708a6314c80cb01e0d1 |
08-Sep-2011 |
Ben Komalo <benkomalo@google.com> |
Revert encryption mapping for device wipes.
External storage volumes that were emulated+encrypted needed to have
their encryption mapping removed so that it doesn't try to encrypt the
volume after formatting them.
This just wires through an argument through vold, and assumes that vold
will do the right thing even if there is no encryption mapping set.
Bug: 5017638
Change-Id: I858fae3d12cb415bc34637f520f71220ad9daaad
torage/AsecTests.java
|
| 112d339673c379b71a989bd33b73648aafe58ce1 |
25-Mar-2011 |
Jesse Wilson <jessewilson@google.com> |
Fix MemoryFile's output stream to advance.
Previously it was not useful.
Change-Id: I0bcc06b65bab33a38a0b0148c020509076a51b1c
http://code.google.com/p/android/issues/detail?id=11415
emoryFileTest.java
|
| 6b888d98f7fffe5b87b3d5421d2f9a119899c7dd |
15-Nov-2010 |
Wink Saville <wink@google.com> |
Move AsyncChannelTest and HierarchicalStateMachineTest to proper directory.
Change-Id: Ifa0f14aad3fee7cad47cdf762c6cff457b56a473
syncChannelTest.java
ierarchicalStateMachineTest.java
|
| 51d10323e9a7374403c2b13befcff5b76c668ca5 |
02-Nov-2010 |
Neal Nguyen <tommyn@google.com> |
am 424963ef: am 5dda76a7: Adding some StorageManager integration test infrastructure and some basic tests.
* commit '424963ef8d46c34d67ea24d25735944c0d87409c':
Adding some StorageManager integration test infrastructure and some basic tests.
|
| 5dda76a72e8bb4630fb5fd38a42e7bceb5b9c954 |
11-Oct-2010 |
Neal Nguyen <tommyn@google.com> |
Adding some StorageManager integration test infrastructure and some basic tests.
More interesting tests to come in the form of host-based tests.
Change-Id: Ifdedf7ef26ed9889871c902af20164df0498cf07
torage/StorageManagerBaseTest.java
torage/StorageManagerIntegrationTest.java
|
| d20a5d6b5a821e28d73eba6502a2135134014a84 |
21-Oct-2010 |
Wink Saville <wink@google.com> |
Add AsyncChannel and AsyncService.
Change-Id: Ie6f9aed58f49defcd1c051611ce791e2e62a9474
syncChannelTest.java
|
| a334e7c72408c4e2805f2427a35d841a60adefc4 |
24-Aug-2010 |
Wink Saville <wink@google.com> |
Allow reliable detection of a message that is in use.
Because the standard Looper.loop code calls Message#recycle it is
imperative that Handler#handleMessage code not attempt to resue
a message it receives. If allowed to do so it will cause bugs that
could be difficult to diagnois.
This change adds Message#flags and uses one bit to reliably detect
a message is in use and throws an error in MessageQueue#enqueueMessage.
This allows early detection of this bug.
Note: This is not new functionality, but the current implementation does
not detect messages that are in use because it uses Message#when != 0
as the detection mechanism. The problem is that a Message#when value of 0
is valid value used to place a message at the front of the queue and is
thus unreliable.
Another option is to change the setting of Message#when in Message#enqueueMessage
so that it is never 0, although that does change subtly a publicly accessible
field.
Yet another option would be to use other fields but all candidates have
similar problems as when in that they are publicly accessible or even
settable such as Message#target.
Change-Id: I040d6e546376f7b1ed1e4daa0d5644cce8bf333a
essageQueueTest.java
|
| ddb2bfeb6e5a383306159672fe81333bf8520776 |
24-Aug-2010 |
Jaikumar Ganesh <jaikumar@google.com> |
Revert "Allow reliable detection of a message that is in use."
This reverts commit 6083d81ce4d67ec632962270fda64ebb9db0d5b1.
Reverting this because it causes runtime to reboot in a loop
if connected to a Bluetooth Headset.
copyFrom() needs to check for the introduced bit too.
essageQueueTest.java
|
| 6083d81ce4d67ec632962270fda64ebb9db0d5b1 |
22-Aug-2010 |
Wink Saville <wink@google.com> |
Allow reliable detection of a message that is in use.
Because the standard Looper.loop code calls Message#recycle it is
imperative that Handler#handleMessage code not attempt to resue
a message it receives. If allowed to do so it will cause bugs that
could be difficult to diagnois.
This change adds Message#flags and uses one bit to reliably detect
a message is in use and throws an error in MessageQueue#enqueueMessage.
This allows early detection of this bug.
Note: This is not new functionality, but the current implementation does
not detect messages that are in use because it uses Message#when != 0
as the detection mechanism. The problem is that a Message#when value of 0
is valid value used to place a message at the front of the queue and is
thus unreliable.
Another option is to change the setting of Message#when in Message#enqueueMessage
so that it is never 0, although that does change subtly a publicly accessible
field.
Yet another option would be to use other fields but all candidates have
similar problems as when in that they are publicly accessible or even
settable such as Message#target.
Change-Id: I2df600537700a3fe206678f38bcae7329751c4e5
essageQueueTest.java
|
| a006b47298539d89dc7a06b54c070cb3e986352a |
14-Apr-2010 |
Bjorn Bringert <bringert@android.com> |
New API and implementation of DB and memory-backed FDs
This depends on a kernel patch that implements read(2)
in the ashmem driver.
Bug http://b/issue?id=2595601
Change-Id: Ie3b10aa471aada21812b35e63954c1b2f0a7b042
emoryFileTest.java
|
| d7b421b4de68d803252a5d9b3cb0106731217ad7 |
05-Aug-2010 |
Kenny Root <kroot@google.com> |
Fix up PackageManager tests
PackageManagerTests was trying to mount and unmount the media without
waiting for the correct state to arrive. It was proceeding with any
state transition.
Some tests had their own volume mounting and unmounting code that was
flawed, so switch it to the more robust mountMedia() and unmountMedia()
implementations.
Change-Id: If464927bb09dd15cb040c6cce195a6ad8452de95
torage/StorageListener.java
|
| f76c56bcaa9df1d1afa711177f813dc63f399795 |
27-Jul-2010 |
Brett Chabot <brettchabot@android.com> |
Frameworks core tests size cleanup.
Adjust test sizes to better align with the test's runtime.
Also do some import cleanup and migrate to non-deprecated classes.
Change-Id: Ib2b190ddbe84f9ea8f5d6d3604bd4855d00df7a9
ileObserverTest.java
ierarchicalStateMachineTest.java
erformanceCollectorTest.java
owerManagerTest.java
|
| a4f3bec29c85ef9e0d07fdd551fe3c50f28b9adc |
19-May-2010 |
Wink Saville <wink@google.com> |
Update docs, add HANDLED, NOT_HANDLED and getCurrentMessage.
The EBNF statemachine description language was to difficult
to remember changed to use a simpler and more obvious psuedo
language.
Added HANDLED and NOT_HANDLED as it makes the psuedo code
more obvious.
Added getCurrentMessage primarily for use by code in enter
so that it can know why the new state is being entered.
Change-Id: I1446e417b77684fbde0020b1da0975eedc57cce4
ierarchicalStateMachineTest.java
|
| 43fe81bc2c186e49b25762450003276a7ed0002d |
07-May-2010 |
Dan Egnor <egnor@google.com> |
Add unit test for passing thread priority & cgroup through Binder.
This test actually exposes some bugs -- the test passes as written, but
certain parts are commented out with references to the bugs in question.
Bug: 2665914
Bug: 2665954
Change-Id: I61220e0efadc4edbb6ad419d26fa1f0f50bbc24c
inderThreadPriorityService.java
inderThreadPriorityTest.java
BinderThreadPriorityService.aidl
|
| a3de74555120cc4dc205a3f93ef44c843b8d64a8 |
25-Mar-2010 |
Brett Chabot <brettchabot@android.com> |
Move PackageManagerTests and AsecTests.
Remove PackageManagerTests test's from continuous due to flakiness.
merged from abandoned master.
Change-Id: I0a542df9df572c37bd1aa987cdc9fb2f95001a7c
torage/AsecTests.java
torage/StorageListener.java
|
| e7be6a85da5be32348f4e83ede195477a7ec1790 |
19-Mar-2010 |
Wink Saville <wink@google.com> |
Allow transitionTo in enter/exit.
bug: 2435366
Change-Id: Id15c5e2cca49ced5ebbda24887f8c490e717f101
ierarchicalStateMachineTest.java
|
| 91fbd56757751a7aca8ef2b4d936e587509e6eef |
18-Mar-2010 |
Wink Saville <wink@google.com> |
Add additional sendMessage methods.
To simplify sending messages add sendMessage methods that take
what and obj as parameters.
Change-Id: Ib22d752eb3cb32fe3dfa8dd2e65915acec3e5db6
ierarchicalStateMachineTest.java
|
| e1e37c632c2deb68f13c92f402c62daaca21afb1 |
16-Mar-2010 |
Brett Chabot <brettchabot@android.com> |
Remove flaky test MemoryFileTest:testPurge from large suite.
Bug 2203775
Change-Id: I4709c0910384f1f2313dc67bfe6e163beaa990e6
emoryFileTest.java
|
| f0f566ec4607376583e59964a6a8a6dcb0265c20 |
11-Mar-2010 |
Wink Saville <wink@google.com> |
Ignore instead of throw errors in QuittingState and reorder some parameters.
Since there could be an arbitrary number of messages in
the queue but Handler/Looper/MessageQueue do not provide
any mechanism for removing "all" messages the best we can
do is ignore. Throwing an error is probably too heavy.
Change-Id: I13c81ac5786484f5b3218885b010de596d943975
ierarchicalStateMachineTest.java
|
| 1b8b98b3db5dcf0b01d1a632aafea076cc91f5a4 |
11-Mar-2010 |
Wink Saville <wink@google.com> |
Add quit and fix HSM EBNF.
Add support for quiting the looper and stopping a thread.
Allow enter/exit at top or bottom of a STATE EBNF.
Fix missing brace in MSG_LIST.
Change-Id: Iddf5ce908008933bf8f0646e844254183da3d1f3
ierarchicalStateMachineTest.java
|
| 1017a134c19b3d296c7c05cf640db4b08816d090 |
17-Feb-2010 |
Bjorn Bringert <bringert@android.com> |
Clean up after failed MemoryFileTest.testPurge()
MemoryFileTest.testPurge() can fail if the process runs
out of file descriptors before the kernel starts purging ashmem areas.
Before, there was no finally block to close the open ashmem
file descriptions, which caused random other tests to fail.
I also changed the size of the memory areas to 10MB, which
should cause it to run out of memory before it runs out of file
descriptors. It now fails with this instead:
java.io.IOException
at android.os.MemoryFile.native_pin(Native Method)
at android.os.MemoryFile.allowPurging(MemoryFile.java:189)
at android.os.MemoryFileTest.testPurge(MemoryFileTest.java:53)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:430)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1447)
I'm not sure why, but it could be that the kernel is purging the just
allocated area instead of an old one. That seems like bug.
See http://b/issue?id=2203775
Change-Id: Ia7930a714378474dd4c2c6709da40c08e715ab6f
emoryFileTest.java
|
| 1a44d5dcabc18cd5ef111f732ccff91683a1a093 |
13-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test cleanup: moving test files from AndroidTests closer to their sources.
Most of these are file moves; a couple notable exceptions are the changes due to the move, and fixing up test code:
- database/DatabaseCursorTest.java
- database/DatabaseStatementTest.java
- net/UriTest.java
idlTest.aidl
idlTest.java
roadcasterTest.java
uildTest.java
ileObserverTest.java
ileUtilsTest.java
andlerTester.java
andlerThreadTest.java
ierarchicalStateMachineTest.java
AidlTest.aidl
dleHandlerTest.java
emoryFileTest.java
essageQueueTest.java
essengerService.java
essengerTest.java
sTests.java
erformanceCollectorTest.java
owerManagerTest.java
ystemPropertiesTest.java
estHandlerThread.java
raceTest.java
|
| 1d3165f10b12165f02b7015ac1a817c5f60e6399 |
12-Jan-2010 |
Neal Nguyen <tommyn@google.com> |
Phase 2 of test file cleanup: relocating test files from FrameworkTest closer to their sources in core.
In addition to the file moves, the package names of the tests have been updated and adjusted to match their new locations.
rightnessLimit.java
|