harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Molotkov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4341) [buildtest][func] 6 tests from functional suite are invalid
Date Thu, 05 Jul 2007 04:05:05 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-4341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Molotkov updated HARMONY-4341:
---------------------------------------

    Attachment: OutputStreamWriterTestShared.patch

> [buildtest][func] 6 tests from functional suite are invalid
> -----------------------------------------------------------
>
>                 Key: HARMONY-4341
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4341
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>         Environment: all
>            Reporter: Vladimir Molotkov
>         Attachments: FileTest.patch, InvocationExceptionTest.patch, LocationTest.patch,
OutputStreamWriterTestShared.patch, PrintStreamTestShared.patch
>
>
> 1) tests/functional/src/test/functional/org/apache/harmony/test/func/api/java/io/File/FileTest:
> Testcase 'testDeleteOnExit' is invalid because it relies on definite deletion order of
nested dirs (marked by deleteOnExit()).
> But this order is unspecified.
> 2) tests/functional/src/test/functional/org/apache/harmony/test/func/api/java/io/share/OutputStreamWriter/OutputStreamWriterTestShared
> Testcase 'testConstructorCharset' is invalid - some character sets can't be used for
output streams
> because they don't provide encoders.
> 3) tests/functional/src/test/functional/org/apache/harmony/test/func/api/java/io/share/PrintStream/PrintStreamTestShared
> Testcase 'testAutoFlush' is invalid - According to the spec PrintStream.print(char) writes
one or more bytes (e.g byte array)
> so printstream will be flushed if auto-flush is enabled. Must use write(int) for test
instead.
> 4) tests/functional/src/test/functional/org/apache/harmony/test/func/api/java/beans/eventhandler/InvocationExceptionTest
> Actually there are two tests. Testcase 'test' in both cases is invalid:
> Case invokeByTypeCasting=false:
> By the spec java.beans.EventHandler.invoke(...) method does not throw any exception.
So we can only expect java.lang.RuntimeException or
> java.lang.Error from this method that possibly wraps any exception thrown from within
invoked target's method.
> Case invokeByTypeCasting=true:
> By the spec java.lang.reflect.Method.invoke(...) throws InvocationTargetException if
the underlying method throws an exception.
> 5) tests/functional/src/test/functional/org/apache/harmony/test/func/api/java/beans/introspector/location/LocationTest
> Testcase 'testUseOnlyImmediateBeanInfo' is invalid because the spec does not restrict
Introspector.getBeanInfo(Class some-class)
> from walking through FULL class hierarchy for caching purposes regardless wether there
is explicit BeanInfo for class being currently
> introspected or not. The spec just says that the method must stop collection of the BeanInfo
for some-class on current
> class (some-class' base or some-class itself) if there is explicit BeanInfo for it.
> Testcase 'testStopClassIsNotParentBean' is invalid because it tests assertion of its
author - not the spec's one.
> There are patchs for all these tests. The tests pass on the RI after patching.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message