river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-301) Move the tests into the JUnit framework inside the main source project
Date Wed, 18 Feb 2009 19:28:02 GMT

    [ https://issues.apache.org/jira/browse/RIVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674756#action_12674756
] 

Jukka Zitting commented on RIVER-301:
-------------------------------------

The following sequence now runs the Ant build in the new integrationtests file:

{code:none}
cd /path/to/jtsk/trunk
ant all jars
cd integrationtests
ant -f integrationtest.xml
{code}

However, the result is a single big jar file that most likely is missing a number of important
pieces like resource files, RMI stubs, etc. Also, the original make build results in 58 individual
jar files in qa/lib. I'm not sure if there's a deep reason for all those jars, so I can't
tell whether we should try to make the Ant build recreate them all.

Another open question is how to best set up and run all these tests. The best reference I
have for now is the following script used by our Hudson CI build:

{code:none}
echo $JAVA_HOME

cd $WORKSPACE/jtsk/trunk
ant clean build.release
ant install.policy

cd $WORKSPACE/qatests/trunk/source/vob/qa/src
gmake clean
gmake
gmake jars
cp $WORKSPACE/qatests/trunk/source/vob/qa/lib/mergedpolicyprovider.jar $JAVA_HOME/jre/lib/ext

$JAVA_HOME/bin/java \
       -cp  $WORKSPACE/qatests/trunk/source/vob/qa/lib/jiniharness.jar:$WORKSPACE/jtsk/trunk/lib/jsk-platform.jar:$WORKSPACE/jtsk/trunk/lib/jsk-lib.jar
\
       -Djava.security.policy=$WORKSPACE/qatests/trunk/source/vob/qa/harness/policy/qa.policy
\
       -Djava.util.logging.config.file=$WORKSPACE/qatests/trunk/source/vob/qa/src/com/sun/jini/test/resources/qa1.logging
\
    com.sun.jini.qa.harness.QARunner \
       $WORKSPACE/qatests/trunk/source/vob/qa/src/com/sun/jini/test/resources/qaHarness.prop
\
       -testJar $WORKSPACE/qatests/trunk/source/vob/qa/lib/jinitests.jar \
       -categories joinmanager \
       -com.sun.jini.qa.harness.serviceMode transient
{code}



> Move the tests into the JUnit framework inside the main source project
> ----------------------------------------------------------------------
>
>                 Key: RIVER-301
>                 URL: https://issues.apache.org/jira/browse/RIVER-301
>             Project: River
>          Issue Type: Task
>          Components: other
>    Affects Versions: AR3
>            Reporter: Tom Hobbs
>         Attachments: RIVER-301.patch, River-301.patch.zip
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The tests donated by SUN live in their own source project and are runnable in a format
that is unfriendly towards IDEs and new developers to the River project.
> This is the proposal to move the test code, mostly unmodified, into the main source directory
whilst shoe-horning it into JUnit 3.  This will allow it to be easily viewable and runnable.
 Such a structure will also reduce the code-compile-test cycle since no JARs will have to
be created in the middle of the cycle and no long command-line incantations.

-- 
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