river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Re: [jira] Commented: (RIVER-301) Move the tests into the JUnit framework inside the main source project
Date Fri, 27 Mar 2009 07:53:47 GMT
Sweet, nice work.

Cheers,

Peter.

Jonathan Costers (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/RIVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689841#action_12689841
] 
>
> Jonathan Costers commented on RIVER-301:
> ----------------------------------------
>
> This is the result for discoverymanager, after about 4 hours:
>
> [java] -----------------------------------------
> [java] 
> [java] # of tests started   = 200
> [java] # of tests completed = 200
> [java] # of tests passed    = 197
> [java] # of tests failed    = 3
> [java] 
> [java] -----------------------------------------
> [java] 
> [java]    Date finished:
> [java]       Fri Mar 27 03:50:13 CET 2009
> [java]    Time elapsed:
> [java]       14194 seconds
>
>
>   
>> 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.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.
>>     
>
>   


Mime
View raw message