| 05fa7802d0874812c234a29745586677ee5837ea |
|
06-Dec-2017 |
Fredrik Roubert <roubert@google.com> |
Integrate ICU4J 60.1 with Android patches into android_icu4j.
Change-Id: I38728116e5d3b9b7f75d6fa2a6f0e71a113e934d
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/duration/DataReadWriteTest.java
|
| 2e13a2bdade5cd0a635f0bd89805931a6fd710da |
|
09-Aug-2017 |
Pete Gillin <peteg@google.com> |
Add sharding annotations to android_icu4j test classes.
Some tests were using too much heap, causing excessive garbage
collection and subsequent timeouts. This change adds an annotation
those specifically, so that they can be run in a separate process,
using their own heaps, so avoiding the timeouts.
Some of these tests were suppressed in the past. The suppressions were
undone when ICU 59 landed, which most likely caused problems on
low-memory devices (b/62374714, whose fix was reverted when ICU 59
landed, and perhaps b/37642683). This change (along with the
AndroidTest.xml change to actually apply the sharding) fixes those
problems. This was tested on fugu on an oc build.
Bug: 62512577
Test: cts-tradefed run cts -m CtsIcuTestCases --primary-abi-only
Change-Id: I013ea26728120bbe3238a7a2dd165606ccad243d
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/duration/DataReadWriteTest.java
|
| f86f25d102340da66b9c7cb6b2d5ecdc0de43ecf |
|
08-Dec-2016 |
Fredrik Roubert <roubert@google.com> |
Integrate ICU4J 58.1 with Android patches into android_icu4j.
Bug: 31328818
Test: CtsIcuTestCases
Test: CtsLibcoreOjTestCases
Test: CtsLibcoreTestCases
Change-Id: Ifd74d26625c7e8c9bb76e88cf419029241117282
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/duration/DataReadWriteTest.java
|
| 3a45e58d9461ee00f295ca8a6a29ef0860559e7e |
|
14-Mar-2016 |
Paul Duffin <paulduffin@google.com> |
Added support for running repackaged Android ICU4J tests using JUnit
Adds JUnit integration classes under android_icu4j/runner that
bridges between ICU4J's custom testing framework and JUnit.
These classes were copied from cts/tests/tests/icu to here,
moved into a new package (to remove cts and ensure that they
do not clash with original classes in cts) and then made
standalone so that they didn't depend on CTS.
The intent is that the original classes will be removed and the
CTS runner will use these classes, either directly or through
standard Android/JUnit integration.
In order for these classes to work with CTS they need to be able
to skip execution, i.e. 'run' the tests in order to fire events
but to not actually execute the tests themselves. This was
previously done using a special parameters class but this uses
the 'standard', in internal Android at least,
AndroidRunnerParams class. As that class is not available on the
host and the host does not require the ability to skip the
execution this provides a dummy implementation that never skips.
This also adds @RunWith annotations to the tests during
repackaging so that they can be run using standard JUnit
runners.
The Android.mk file has instructions on how to run using both
JUnit and the ICU4J test framework.
There are a number of issues with running tests under JUnit but
they will be fixed in follow on changes.
Bug: 22023363
Change-Id: Iac1221c12cc7194277db49b9a013d427d9533b36
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/duration/DataReadWriteTest.java
|
| aefe4d1f8f1773ead1a52f7a5d2c9e0009353600 |
|
26-Feb-2016 |
Paul Duffin <paulduffin@google.com> |
Add repackaged version of the ICU tests
Adds a new android-icu4j-tests target to build the repackaged
tests. The repackages tests were generated by running the
following script which was modified to repackage the tests in
addition to the source and sample.
tools/srcgen/generate_android_icu4j.sh
Bug: 22023363
Change-Id: I3c6e65ba6a4d24055343460a023d6671585146f5
/external/icu/android_icu4j/src/main/tests/android/icu/dev/test/duration/DataReadWriteTest.java
|