summaryrefslogtreecommitdiffstats
path: root/luni/src/test
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | Fix getISO3Country and getISO3Language.Narayan Kamath2014-06-181-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For backward compatibility, locales constructed with 3 letter countries and languages must return those languages and countries from these methods. With our strict language tag interpretation, these were being omitted or transformed to und. We fix this by passing only the language code (or the country code with a fixed language) down to ICU, which will then deal with it correctly. bug: 15638049 Change-Id: I517a82496a2a4c36b1ae9234f7d2d4eb89b34ffe
* | | | Merge "Relax KeyPairGeneratorTest"Neil Fuller2014-06-171-8/+43
|\ \ \ \
| * | | | Relax KeyPairGeneratorTestNeil Fuller2014-06-181-8/+43
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | Changing KeyPairGeneratorTest to handle different number of providers. Bug: 5513723 Change-Id: I74ba53d9ebe8197bf4aeeb8f5742b961d5285bfb
* | | | Alter regression test for bug 71369 now the issue is understoodNeil Fuller2014-06-181-3/+10
|/ / / | | | | | | | | | | | | | | | | | | | | | The code was most likely fixed by an ICU update. This was added to prevent regression. See the bug for details. Bug: 71369 Change-Id: I8896334dfeac3a1dcb6379ac58510ede60f6b7c7
* | | Merge "Add a test for bug 71369"Neil Fuller2014-06-171-0/+15
|\ \ \ | |/ / |/| |
| * | Add a test for bug 71369Neil Fuller2014-06-171-0/+15
| |/ | | | | | | | | | | The bug appears not to be present any more. Change-Id: I83999e7ded4818048c386b41dd879d56edad18e7
* | Merge "Pass BCP-47 tags and not Locale.toString results to ICU."Narayan Kamath2014-06-102-12/+118
|\ \
| * | Pass BCP-47 tags and not Locale.toString results to ICU.Elliott Hughes2014-06-162-12/+118
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ICU can't handle the new toString forms for scripts etc. and it's also guaranteed to deal with BCP-47 tags correctly. Most of the changes in this patch are required to keep backwards compatibility for getDisplayCountry string etc. in the face of the transformations toLanguageTag performs. A few tests were changed, but for the better. The tagalog -> filipino charlie foxtrot will be dealt with in a follow up change. Co-Authored-By: Narayan Kamath <narayan@google.com> Change-Id: Ia7f26d92a0e38c4bbb1d839c0fbd8ad16a473bf5
* | Fix bogus define checks and a typo.Narayan Kamath2014-06-131-0/+31
|/ | | | | | | | | | | | | | | RT_* constants are enum members in the UAPI so we can't use #define checks for them. Also fix a typo in the define check for an IFA_ constant. More generally, we should get rid of all these conditional checks for target builds because we know what version of the UAPI we have in bionic. We should move these conditional checks under #if HOST_BUILD or something similar. bug: 15602893 Change-Id: I3affc10773ade4dac68c176f79962ca8ad312579
* Implement Locale.toLanguageTag without ICU support.Narayan Kamath2014-06-121-1/+1
| | | | | | | | | | | | This is the first part of an effort to avoid having to construct and parse ICU locale IDs and to instead use language tags as inputs to all ICU APIs. Only one minor unit test adjustment was required, and that change brings the test closer in line with the spec. Change-Id: I8abc0e3b868dd73e4fb9e36b6db19853eb99e6ac
* Merge "Extract non-API locale tests into a separate test class."Narayan Kamath2014-06-102-106/+129
|\
| * Extract non-API locale tests into a separate test class.Narayan Kamath2014-06-112-106/+129
| | | | | | | | | | | | | | | | | | Several ICU tests and tests of ICU related internal methods have snuck into LocaleTest. Split them into a separate class to make it easier to run this test against older branches and across refactorings. Change-Id: I16db4a930b39e5dd4af16d99aa4ecd1be7cf948f
* | Merge "Tests for Runtime.*Memory()"Neil Fuller2014-06-101-26/+0
|\ \
| * | Tests for Runtime.*Memory()Neil Fuller2014-06-101-26/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The docs describe a condition we do not test for. The freeMemory / totalMemory tests have been consolidated into a single test and joined by an additional assertion for maxMemory(). The test for freeMemory from OldRuntimeTest has been tidied up and moved to RuntimeTest. Bug: 15507122 Change-Id: I4343215fb7f6b441613e25d3844d67812f5b5e94
* | | Fix DatagramMulticastChannelTest so it works better on hammerheadNeil Fuller2014-06-101-345/+392
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some android devices have a WiFi-direct interface (p2p0) that probably shares underlying hardware with the standard wireless interface (wlan0). On hammerhead, when Wifi-direct is disconnected this interface appears to (only) have an IPv6 address and is "up" and "support multicast". The test was not tested on this hardware when it was written. Mako devices have the same behavior but the wlan0 interface most likely discovered first. The ordering of interfaces may also not be stable. The other breakages were due to implicit assumptions that the device supports both IPv4 and IPv6 on a single interface. The tests also rely on the IP_MULTICAST_LOOP option to receive packets sent out. There were some other bugs that were probably the result of assuming that when the interface was left unspecified the device would route outgoing packets via the interface the test was listening on. With multiple interfaces available those tests were flaky. Bug: 15509450 Change-Id: I33f71e26379a53334dce9991043c3a9a21000d02
* | Shard the _getInstance test and skip the DH tests.Neil Fuller2014-06-091-50/+70
|/ | | | | | | | | | The _getInstance test was suppressed previously because it took too long to complete. This re-enables parts of the test but temporarily skips the DH algorithm until it can be investigated further. Bug: 5513723 Change-Id: Ia211de51f8def5b710c1d2a164f1ec70e474fc7a
* Merge "Fix ZoneInfoDBTest.testGoodOverride"Neil Fuller2014-06-031-15/+17
|\
| * Fix ZoneInfoDBTest.testGoodOverrideNeil Fuller2014-06-021-15/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When executed under the CTS environment some of the tests in ZoneInfoDBTest assumed: 1) The device was booted with all tzinfo files present and that they don't change (i.e. so the runtime's static TimeZone singleton reflects the contents of the file system at the time the test is executed). 2) The number of timezone IDs in /data/misc/zoneinfo/tzdata, /system/usr/share/zoneinfo/tzdata are the same (if assumption 1 holds). This change modifies the tests to only use the (unchanging) /system/usr/share/zoneinfo/tzdata file and avoid use of the TimeZone class. Bug: 15382201 Change-Id: I8d3b1ea52a2147e7afaa302803c834539bd01db9
* | Merge "Fix for flakiness in URLConnectionTest.testServerShutdownOutput"Neil Fuller2014-05-301-0/+6
|\ \
| * | Fix for flakiness in URLConnectionTest.testServerShutdownOutputNeil Fuller2014-05-281-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | Flakiness reported by Junjie.Hu <junjie.hu@mediatek.com> This fix relies on changes to MockWebServer to provide deterministic ordering of responses. Change-Id: I4f296fa2f8d227876f52c69e22001f4e0d7b4ffd
* | | Merge "Document and assert support for TLS-PSK cipher suites."Alex Klyubin2014-05-293-4/+137
|\ \ \ | |_|/ |/| |
| * | Document and assert support for TLS-PSK cipher suites.Alex Klyubin2014-05-273-4/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This CL updates the Javadoc of SSLSocket and SSLEngine to list the now supported TLS-PSK cipher suites. It also adds tests to assert that these cipher suites are actually supported by SSLSocket and SSLEngine. Bug: 15073623 Change-Id: I8e59264455f980f23a5e66099c27b5b4d932b9bb
* | | Merge "Fix NetworkOnMainThreadException in KeyStoreTest"Neil Fuller2014-05-281-21/+27
|\ \ \ | |/ / |/| |
| * | Fix NetworkOnMainThreadException in KeyStoreTestNeil Fuller2014-05-281-21/+27
| |/ | | | | | | | | | | | | | | | | | | A quick fix for KeyStoreTest. Commit 1b6a2f56cf25fcbd0e2311be58d8577565622cf3 moved some code around causing the static initializer of the test to access the network, which is forbidden in CTS tests. Change-Id: I8addfa8f3b0d801cb90b9f9bb7d2707c4fc3f62f
* | Merge "Fix testCalendarSerialization for all locales"Neil Fuller2014-05-271-1/+3
|\ \
| * | Fix testCalendarSerialization for all localesNeil Fuller2014-05-231-1/+3
| |/ | | | | | | | | | | | | | | | | The test was passing on vogar but not under CTS on a local device. The test was sensitive to the default locale so failed when run on devices with a non-US locale. Change-Id: I202b2dec417bb8249eb9d6f69240bd120efb07f9
* | Merge "Adding more tests around System properties"Neil Fuller2014-05-231-1/+57
|\ \
| * | Adding more tests around System propertiesNeil Fuller2014-05-211-1/+57
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is in preparation for clearing all system properties between CTS tests to reduce test leakage. The code in the test runner that explicitly sets certain values can also be removed now that those properties have been made immutable. Note: As part of this I discovered that java.io.tmpdir is still mutable under the Zygote and immutable under vogar (where it is set as a command-line arg). This means that calling System.getProperties().clear() or System.setProperties(null) removes the property entirely under an Android app but not under vogar. Change-Id: If0361b138666909b21de9d6b8a73a584e9390550
* | DigestTest: reduce flakiness by having more iterationsKenny Root2014-05-211-1/+1
|/ | | | | | | | This fails every once in a while sinch this isn't a rigorous benchmark, but try to combat it by having more iterations so the measurement has more time to stabilize. Change-Id: I4336d0d670e1e666e5bb75788228651f563eb59a
* Merge "Fix typo in test"Neil Fuller2014-05-211-1/+1
|\
| * Fix typo in testNeil Fuller2014-05-211-1/+1
| | | | | | | | | | | | | | The test is supposed to be testing afterLast() not beforeFirst(). Change-Id: Ie36c55ec4d5a09e85ba6a6c5e2eeb037f34422ce
* | Keep Preferences tests workingNeil Fuller2014-05-214-3/+76
|/ | | | | | | | Apply changes made as part of I6019441c65b398376d84264f1e4c9776507533eb more widely. Bug: 15105787 Change-Id: I2e44487b1561dd564bfa41d65995a61091b011eb
* Merge "Deprecate use of BrokenTest and SideEffect"Neil Fuller2014-05-2113-31/+16
|\
| * Deprecate use of BrokenTest and SideEffectBrett Chabot2014-05-2113-31/+16
| | | | | | | | | | | | | | | | | | Use expectations files instead. (cherry picked from commit 6a6b612286976cc185c898803fe51e4e062bd9eb) Bug: 12924356 Change-Id: I9b7e71805a80176c873cffe46bed65f81de1903d
* | Merge "Add regression tests for null arguments to DecimalFormat."Elliott Hughes2014-05-201-0/+63
|\ \
| * | Add regression tests for null arguments to DecimalFormat.Elliott Hughes2014-05-201-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This was already fixed last year by 3909f6dba0812caee25a8779dcbf4c50ce9b19c7 under a different bug, but this extends the testing to all methods that could take a null argument. Bug: https://code.google.com/p/android/issues/detail?id=62269 Bug: 15081434 Change-Id: I30c97360a868e412649850109e24f2707c072a30
* | | Merge "Fix OldURLClassLoaderTest#test_findResource_String"Neil Fuller2014-05-201-26/+10
|\ \ \
| * | | Fix OldURLClassLoaderTest#test_findResource_StringNeil Fuller2014-05-201-26/+10
| | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The test broke because Support_TestWebData was changed to provide the /test3 URL for a different test (Ib43e68a2536c2602b4c7ee0cda68fa1f90045f57). Changing the URL to test9999 fixes it. The OldURLClassLoaderTest is unpleasant but I haven't touched it beyond correcting the test and fixing some of the more obvious style / import problems that my IDE pointed out. Change-Id: I42b3e8ab69cdef65ee381efbf1988cfdfa359868
* | | Merge "Fix test_isWhitespace_against_icu4c"Neil Fuller2014-05-201-2/+16
|\ \ \
| * | | Fix test_isWhitespace_against_icu4cNeil Fuller2014-05-201-2/+16
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | ICU4C and the RI disagree about one character. Add the special case to the test so it can pass. Also fix isSpaceChar_against_icu4c so it asserts something, and add the special case there too. Bug: 9690863 Change-Id: I389690e5c598b9e2f04015b0bc14799b163a6adf
* | | Merge "Fix InetAddressTest"Neil Fuller2014-05-201-3/+12
|\ \ \ | |_|/ |/| |
| * | Fix InetAddressTestNeil Fuller2014-05-191-3/+12
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: test_getByName test_isNumeric test_parseNumericAddress Change Ic42173b7b06e8536e8c4331087720d7df1e1681a (made in early 2011) modified handling of "obsolete" numeric IP addresses. At least since then, Octal addresses (those with leading 0's) have been parsed as decimal values. The tests were written to expect Octal values to be rejected and 0177.00.00.01 was expected to be treated as an invalid address. If interpreted as a decimal (177.0.0.1) it is fine. The tests have been updated to test a more obviously incorrect value and the docs have been updated to document how Android and the RI differ. Bug: 4539262 Change-Id: I5f9dce6b1accd81dda1348718fe0c74b03c27c29
* | Merge "DirectByteBuffer: allow 0-size MappedByteBuffers starting at NULL"Lajos Molnar2014-05-191-1/+1
|\ \
| * | DirectByteBuffer: allow 0-size MappedByteBuffers starting at NULLLajos Molnar2014-05-161-1/+1
| |/ | | | | | | | | Bug: 14297827 Change-Id: I53ae796f9a59c70cc8250477ab51c57ea728e43b
* | Fix the expected failure when an array of void is attempted to be created.Ian Rogers2014-05-181-2/+2
|/ | | | | | NoClassDefFoundError is the RI behavior. Change-Id: Ia03b585def9f772aeb17f1cdec4da2d0c807ede3
* Merge "Removing data hacks from ICU root.txt"Neil Fuller2014-05-157-60/+108
|\
| * Removing data hacks from ICU root.txtNeil Fuller2014-05-147-60/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the upstream ICU data was modified to support special short codes (e.g. PST, CET) so that they were recognized when parsing/formatting in all locales with SimpleDateFormat.parse()/format(). In an effort to more-closely replicate ICU this change does *not* introduce special casing for short / abbreviated names from Java APIs. This may have impact for applications that use Date.toString() (but not Date.parse()), SimpleDateFormat.parse(), SimpleDateFormat.format(), and anything that uses TimeZone methods that deal in formatting and zone strings (e.g. getZoneStrings(), getDisplayName()). Details: Date.parse() is unaffected because it handles abbreviated names only, is not internationalized and contains a set of recognized strings. Date.toString() is affected because it relies on SimpleDateFormat for formatting. ICU still supports abbreviated / short names for locales where those terms are considered unambiguous for residents of that locale. For example, "PST" is still parsed / formatted in Locale.US when using SimpleDateFormat. However, with this change "PST" will not be parsed/formatted other locales such as Locale.FRANCE, Locale.UK. If SimpleDateFormat.format() / TimeZone.getDisplayName() cannot find a short / abbreviated name for a timezone in the specified/defaulted locale, then a GMT offset is output as per the docs. Of particular note are methods that rely on Locale.getDefault() and/or Locale.getTimeZone(). Most user-facing usecases are expected to be unaffected. For example, US users will continue to see / enter PST. Applications that were previously parsing a date string containing (for example) PST but relying on the default locale will start seeing failures. Most of the changes are in tests that were hardcoding expected strings or relying on the default locale. This change is associated with a change in external/icu4c: I04acd15c62d49c0cf30cc63f60db320bdb8e22e9 This commit also includes minor test changes related to parsing/formatting dates where the default device locale is assumed to be US (or other English-speaking locale). Date-related tests that were relying on the default locale and broke when it was set to a non-English script are now explicitly setting it. Note: The tests all rely on the CtsTestRunner / Vogar resetting the default Locale / TimeZone between each test. Bug: 11413756 Change-Id: I9ae6397cf5335ef325aedb6472d0d66a6127e1dd
* | Fix a test that assumes Locale.getDefault() == Locale.USNeil Fuller2014-05-141-15/+14
|/ | | | | | | | If the device is set to non-English locale this fails. Setting the default locale explicitly makes the tests clearer (the CtsTestRunner / vogar) sets it back again. Change-Id: I4c197f4823115f178acc51a62a64855b790011b4
* DirectByteBuffer: add setAccessible()Lajos Molnar2014-05-121-0/+144
| | | | Bug: 14297827 Change-Id: I726f16f9a15f894b99a93c84aca820f5c1b994e5
* Better protection against accessing freed DirectByteBuffersLajos Molnar2014-05-121-16/+29
| | | | | | | | | | | Expand preventing access of freed buffers, so duplicated ByteBuffers also become inaccessible when the original buffer is freed. Throw IllegalStateException in ByteBuffer.put(ByteBuffer) when either source or destination buffer is inaccessible. Bug: 11512044 Change-Id: Idd2f4ef1f3d66b4209441bf4014ccd4aad9d850b
generated by cgit v1.1 at 2025-03-24 16:04:06 +0000