f9a80cbbfe5585772ea16fddfeb728c74bc04b2d |
|
23-Sep-2015 |
Mitchell Wills <mwills@google.com> |
Fix TimeUtils.formatDuration for exactly one of a unit Previously printing a duration where a unit (except ms) was one and the next smallest unit was zero would result in the duration being being expressed in the next smallest unit. For example 1m0s0ms would be formatted as 60s0ms. Update testFormatHugeDuration to supporting times > 999 days The implementation was fixed in 3d1933c45fe9ba2389ebd166d96abeceab1971d1 Change-Id: I9d609f7a0f82755ea653a205293a6e3785a10d1e
/frameworks/base/core/tests/coretests/src/android/util/TimeUtilsTest.java
|
eaaf396169abdbd213565cacb37dc0c9c391b365 |
|
21-Jul-2012 |
Jeff Sharkey <jsharkey@android.com> |
Avoid emitting broken ASCII. Bug: 6131887 Change-Id: Iff13573aad8128cc7ae3613ab718c81e6d0862a1
/frameworks/base/core/tests/coretests/src/android/util/TimeUtilsTest.java
|
901b3796fd0954cc4b01bf95dbcbd88d87414e84 |
|
23-Nov-2010 |
Bjorn Bringert <bringert@android.com> |
Don't drop zeros in the second position in formatDuration() Bug: 3223250 Change-Id: I462c96af51cc052f9df1dc3d2c668551b10155ea
/frameworks/base/core/tests/coretests/src/android/util/TimeUtilsTest.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
/frameworks/base/core/tests/coretests/src/android/util/TimeUtilsTest.java
|