harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-57) Contribution of unit test code for a number of components
Date Wed, 15 Mar 2006 11:49:39 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-57?page=all ]
Tim Ellison resolved HARMONY-57:

    Resolution: Fixed

Thank you George and Mark,

The contribution has been applied at repo revision 386058.

Please check that the contribution was applied as you expected.

> Contribution of unit test code for a number of components
> ---------------------------------------------------------
>          Key: HARMONY-57
>          URL: http://issues.apache.org/jira/browse/HARMONY-57
>      Project: Harmony
>         Type: Test
>   Components: Contributions
>  Environment: All
>     Reporter: George Harley
>     Assignee: Tim Ellison
>  Attachments: 01.harmony.57.integration.sh, 02.harmony.57.integration.diff, Harmony-Unit-Tests.zip
> Zip file containing JUnit tests for the following Harmony components :
> * archive
> * luni
> * nio_char
> * text
> The contents of this zip have been laid out with the current classlib directory structure
of the Apache Harmony SVN repository in mind. A version of enhanced/classlib/trunk/make/build-java.xml
is included containing new Ant targets to compile and run the tests. 
> Some of the tests depend on the availablity of additional resources (text files, jars,
etc). These resources are included in the zip along with configuration instructions. 
> A small number of the 3000+ test cases are known to fail when run against a built Harmony.
The identities of these tests, plus some additional information on them have been listed in
the file <ZIP_EXTRACT_DIR>/Harmony/Harmony_Tests/src/test/resources/config/jcltest-excludes.xml
. This file can be used during the running of the tests to purposely exclude the set of known
failures. Information on how this is accomplished is also included. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message