Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <16100406.1162339817030.JavaMail.root@brutus>
Date: Tue, 31 Oct 2006 16:10:17 -0800 (PST)
From: "Daniel John Debrunner (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2006) Add JUnit and JUnitReport task as a
 target in Ant script
In-Reply-To: <8406890.1161883999186.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-2006?page=comments#action_12446126 ] 
            
Daniel John Debrunner commented on DERBY-2006:
----------------------------------------------

Given that flat output and the out of memory errors seen, I wonder if the ant targets should be at a lower suite granurality than suites.All.
There could be a target that ran the various _Suite tests as separate junit invocations, mimicing the suites.All.


> Add JUnit and JUnitReport task as a target in Ant script
> --------------------------------------------------------
>
>                 Key: DERBY-2006
>                 URL: http://issues.apache.org/jira/browse/DERBY-2006
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.3.0.0
>         Environment: Any
>            Reporter: Yip Ng
>         Attachments: derby_2006_v1.diff, derby_2006_v2.diff, derby_2006_v3.diff, example_output.zip
>
>
> Ant has an optional tasks called JUnit and JUnitReport that runs JUnit tests and produces JUnit report respectively.  It will be nice to have these mechanism incorporated into the Ant script so one can easily kick off a JUnit test and view the result. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira