Do you mean this?
if (result == null ||
expected != null &&
!result.equals(expected)) {
throw new RuntimeException(...);
}
Masayoshi
On 5/15/2013 1:06 AM, Naoto Sato wrote:
Well, I just want to make sure that, in case of expected == null,
It does sound like a bug. Moved the web incidents into a JDK bug (8014558)
Naoto
On 5/14/13 5:30 AM, Anthony Petrov wrote:
Hi Deven,
I'm copying i18n-dev@ because they manage the IM code.
As to a test, jtreg supports manual tests. See [1] for a lot of tips
about using manual tests. An example
Well, I just want to make sure that, in case of expected == null, the
result value still is non null, which assures that FALLBACK provider has
kicked in. So I think checking "result != null" is still needed.
Naoto
On 5/13/13 5:15 PM, Masayoshi Okutsu wrote:
I see. The test case should get the
Hi Deven,
I'm copying i18n-dev@ because they manage the IM code.
As to a test, jtreg supports manual tests. See [1] for a lot of tips
about using manual tests. An example of a manual test is at:
jdk/test/java/awt/event/MouseEvent/SpuriousExitEnter/SpuriousExitEnter.java
[1] http://openjdk.ja