Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 53651 invoked from network); 3 Oct 2007 09:25:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Oct 2007 09:25:53 -0000 Received: (qmail 71179 invoked by uid 500); 3 Oct 2007 09:25:42 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 70863 invoked by uid 500); 3 Oct 2007 09:25:41 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 70852 invoked by uid 99); 3 Oct 2007 09:25:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 02:25:41 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [192.6.10.2] (HELO colossus.hpl.hp.com) (192.6.10.2) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 09:25:40 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by colossus.hpl.hp.com (Postfix) with ESMTP id 903846B9EC for ; Wed, 3 Oct 2007 10:25:18 +0100 (BST) X-Virus-Scanned: amavisd-new at hplb.hpl.hp.com Received: from colossus.hpl.hp.com ([127.0.0.1]) by localhost (colossus.hpl.hp.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id khL2kSztqLWH for ; Wed, 3 Oct 2007 10:25:17 +0100 (BST) Received: from ha-node-br2.hpl.hp.com (ha-node-br2.hpl.hp.com [16.25.144.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by colossus.hpl.hp.com (Postfix) with ESMTP id BA7696B9E9 for ; Wed, 3 Oct 2007 10:25:16 +0100 (BST) Received: from [16.25.171.118] ([16.25.171.118]) by ha-node-br2.hpl.hp.com (8.14.1/8.13.4) with ESMTP id l939P12F027726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Oct 2007 10:25:02 +0100 (BST) Message-ID: <47035FED.3030801@apache.org> Date: Wed, 03 Oct 2007 10:25:01 +0100 From: Steve Loughran User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Ant Developers List Subject: Re: JUnit Filter, extension of JUnitTask? References: <1191401291.6644.20.camel@Rutger.Lubbers.Laptop> In-Reply-To: <1191401291.6644.20.camel@Rutger.Lubbers.Laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HPL-MailScanner-Information: Please contact the ISP for more information X-HPL-MailScanner: Found to be clean X-HPL-MailScanner-From: stevel@apache.org X-Virus-Checked: Checked by ClamAV on apache.org Rutger Lubbers wrote: > Hi, > > JUnit (since 4.?) allows filtering of the tests to be run. It would be > nice to allow ant build scripts to use this filter capacity. This would > allow developers to run a (small, fast running) set of tests, while the > integration or production build runs extra test sets. The filtering only > works with JUnit 4 test code. > > I've changed a few source files (of ant 1.7.0) and added two. It works > fine (here). It requires (at the moment) a typedef of the filter: > classname="org.apache.tools.ant.taskdefs.optional.junit.JUnitFilter"/> > > and can be used as follows: > > classname="com.example.JUnitDBFilter" > properties="dbtest"/> > > > I would like to know if you find this useful (enough) for inclusion. > Would someone like to see the code and comment on it? > > Thanks & Kind regards, JUnit4 stuff is something I'd like to work on, either as a separate antlib or as somethig in Ant, presumably in the package org.apache.tools.ant.taskdefs.optional.junit4 1. I was planning a new task for it, one that is a superset of ; this filtering could go in there. 2. I'm planning to extend the xml test results to include more data (from junit4, antunit, and anything else compatible) -add skipped tests: count+details -allow every test to have a description, a URL and a bugID (well, a list of them) -dump more machine details into a per-machine file when we do the test run; I think the filter stuff could go in there; why not add it as an enhancement request (with code) to bugzilla under issues.apache.org? -steve -- Steve Loughran http://www.1060.org/blogxter/publish/5 Author: Ant in Action http://antbook.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org