[jira] Issue Comment Edited: (RIVER-301) Move the tests into the JUnit framework inside the main source project

["Jonathan Costers (JIRA)" <ji...@apache.org>]

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

Jonathan Costers edited comment on RIVER-301 at 9/27/09 9:52 AM:
-----------------------------------------------------------------

In the mean time, we have:
- integrated the QA suite and tests
- ran most QA tests and verified them
- re-enabled the hello example
- updated most distribution documentation

Things to do:
- update docs for QA subproject (esp. README.txt)
- run more QA tests on all platforms
- enable running the jtreg tests (thinking about a way to do it)

      was (Author: jcosters):
    In the mean time, we have:
- integrated the QA suite and tests
- ran most QA tests and verified them
- re-enabled the hello example
- updated most distribution documentation

Things to do:
- update docs for QA subproject (esp. README.txt)
- run more tests on all platforms
  
> 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
>            Assignee: Jonathan Costers
>         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.