Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 94403 invoked from network); 2 Feb 2006 09:36:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Feb 2006 09:36:07 -0000 Received: (qmail 256 invoked by uid 500); 2 Feb 2006 09:36:05 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 227 invoked by uid 500); 2 Feb 2006 09:36:04 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 218 invoked by uid 99); 2 Feb 2006 09:36:03 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 01:36:03 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.98.31] (HELO brmea-mail-1.sun.com) (192.18.98.31) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 01:36:03 -0800 Received: from phys-epost-1 ([129.159.136.14]) by brmea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id k129ZgSD015898 for ; Thu, 2 Feb 2006 02:35:42 -0700 (MST) Received: from conversion-daemon.epost-mail1.sweden.sun.com by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IU100D01ZNMFL@epost-mail1.sweden.sun.com> (original mail from Andreas.Korneliussen@Sun.COM) for derby-dev@db.apache.org; Thu, 02 Feb 2006 10:35:41 +0100 (MET) Received: from [129.159.112.247] (khepri35.Norway.Sun.COM [129.159.112.247]) by epost-mail1.sweden.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTPA id <0IU100CNZZZHJM@epost-mail1.sweden.sun.com> for derby-dev@db.apache.org; Thu, 02 Feb 2006 10:35:41 +0100 (MET) Date: Thu, 02 Feb 2006 10:35:41 +0100 From: Andreas Korneliussen Subject: Re: Features of the JUnit test execution harness In-reply-to: To: derby-dev@db.apache.org Reply-to: Andreas.Korneliussen@Sun.COM Message-id: <43E1D26D.7000908@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) References: <43D634B8.7060706@Sun.COM> <43D679D1.5040707@sun.com> <43D67D56.4030108@apache.org> <43D68152.9010201@Sun.com> <43DFF286.9060706@Sun.COM> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Myrna van Lunteren wrote: > On 1/31/06, *Kristian Waagan* > wrote: > > Differences in output should be irrelevant. Although not what you > mentioned above, the issue of (execution) control is very relevant. The > logic for running the tests multiple times, each time with a different > setup/environment must be located somewhere. I think Andreas' proposal > of introducing a separate JUnit test type (see > http://www.nabble.com/running-JUnit-tests-t887682.html#a2300670) makes > sense, as it gives us more freedom w.r.t. handling of JUnit tests. > > > Yes, that proposal made sense to me. I personally like the approach of > having a class for various/different configurations. Although that could > get out of hand. > > Does this 'throw away' the work that Rick is doing on DERBY-874? > I think the work currently done on DERBY-874 was mainly to improve the DerbyJUnitTest's JavaDoc, and to log exceptions. So I would not throw that away. However I do propose to change DerbyJUnitTest to move out everything about configuration into a separate class. > Following Andreas' approach we'd still be able to run the individual > tests separately, yes? > Yes - definetly. Andreas