river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Costers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-301) Move the tests into the JUnit framework inside the main source project
Date Fri, 17 Apr 2009 20:04:16 GMT

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

Jonathan Costers commented on RIVER-301:

Forget the attached patch, changes are being committed to the trunk as we speak.

- Added targets to call multiple variations of the QA test run
- Integrated classdep replacement code and removed JDK tools.jar dependency

- check out the trunk to <trunk>
- cd <trunk>
- 'ant all' to build everything
- 'ant release' to build everything and create release packages
- 'ant qa.run' to run a sample QA test run (assumes everything is built)

Work In Progress:
- Move hello example to separate source tree (same way as /qa): separate JIRA issue TBD
- documentation

> 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: integrationtest.xml, RIVER-301-JC-5.1.patch, RIVER-301-JC-6.0.patch.tar.gz,
RIVER-301.patch, RIVER-301.patch, River-301.patch.zip, River-build-qa5.patch
>   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.

View raw message