Ok, I went ahead and added a new task called test-subset which lets you 
run individual or subsets of tests.  The syntax looks like this:

build -Djunit.test=**/ResourceLimiting*TestCase.class test-subset

I also merged the test and test-report tasks into a single task.  They 
were testing different things because people had not been modifying both 
of them over time.
The way it is now, the test reports are always generated by the test 
task, but the TEST-*.xml files are deleted to remove clutter.

When I was merging the tasks, I noticed that the test task was excluding 
the following tests, while the test-report task was not.  Currently this 
code is commented out so they always run.

         <exclude 
name="org/apache/avalon/excalibur/naming/rmi/test/RMIContextTestCase.class"/> 

         <exclude 
name="org/apache/avalon/excalibur/logger/test/LogKitManagementTestCase.class"/> 

         <exclude 
name="org/apache/avalon/excalibur/concurrent/test/ReadWriteLockTestCase.class"/> 

         <exclude 
name="org/apache/avalon/excalibur/monitor/test/MonitorTestCase.class"/>

Right now there is 1 failure in the 
org.apache.avalon.excalibur.monitor.test package and 2 errors in the 
org.apache.avalon.excalibur.i18n.test package.

Cheers,
Leif

Peter Donald wrote:

>On Thu, 24 Jan 2002 15:20, Leif Mortenson wrote:
>
>>Glad I asked then.  It looks like like the junit task allows you to
>>specify two formatters.
>>So I can make it output both text and xml reports.
>>
>>As I was adding that though I realized that there is already another
>>task called
>>test-reports which already does this.  How would you feel about removing
>>the test-reports
>>task in favor of the method above to reduce code duplication?
>>
>>If there is concern about the clutter caused by both text and xml files
>>being in the reports
>>directory, that problem could be solved by deleting the test xml files
>>after the junittest
>>task has completed.
>>
>>
>>I like the idea of being able to run individual tests, so I added a new
>>task test-subset
>>which expects a property junit.test for the test(s) to be run.
>>
>>I'm including the diff of that.
>>
>>Opinions?
>>
>
>+1 - go for it ;)
>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to