Return-Path: 
 <jdo-dev-return-85-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org>
Delivered-To: apmail-db-jdo-dev-archive@www.apache.org
Received: (qmail 19617 invoked from network); 23 Feb 2005 22:54:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 23 Feb 2005 22:54:52 -0000
Received: (qmail 91926 invoked by uid 500); 23 Feb 2005 22:54:52 -0000
Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jdo-dev-help@db.apache.org>
List-Unsubscribe: <mailto:jdo-dev-unsubscribe@db.apache.org>
List-Post: <mailto:jdo-dev@db.apache.org>
List-Id: <jdo-dev.db.apache.org>
Reply-To: jdo-dev@db.apache.org
Delivered-To: mailing list jdo-dev@db.apache.org
Received: (qmail 91913 invoked by uid 99); 23 Feb 2005 22:54:52 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from brmea-mail-4.Sun.COM (HELO brmea-mail-4.sun.com) (192.18.98.36)
  by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 23 Feb 2005 14:54:50 -0800
Received: from phys-mpk-1 ([129.146.11.81])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j1NMsmKw010305
	for <jdo-dev@db.apache.org>; Wed, 23 Feb 2005 15:54:48 -0700 (MST)
Received: from conversion-daemon.mpk-mail1.sfbay.sun.com by
 mpk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 id <0ICD00901ZMIHN@mpk-mail1.sfbay.sun.com>
 (original mail from Michelle.Caisse@Sun.COM) for jdo-dev@db.apache.org; Wed,
 23 Feb 2005 14:54:48 -0800 (PST)
Received: from [129.150.24.158]
 (vpn-129-150-24-158.SFBay.Sun.COM [129.150.24.158]) by
 mpk-mail1.sfbay.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 with ESMTP id <0ICD00AQ0ZNA2D@mpk-mail1.sfbay.sun.com> for
 jdo-dev@db.apache.org; Wed, 23 Feb 2005 14:54:47 -0800 (PST)
Date: Wed, 23 Feb 2005 14:55:58 -0800
From: Michelle Caisse <Michelle.Caisse@Sun.COM>
Subject: Re: JDO TCK TestRunner ideas
In-reply-to: <421D054D.4030005@spree.de>
To: jdo-dev@db.apache.org
Message-id: <421D09FE.7070404@sun.com>
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/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2)
 Gecko/20040803
References: <421D054D.4030005@spree.de>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

This sounds like quite a good solution, Michael.

-- Michelle

Michael Bouschen wrote:

> Hi,
>
> I had an action item to investigate how to extend the JDO TCK 
> TestRunner  such that the same test class can be run in multiple 
> configurations. These are possible configuration parameters:
> - identity setting (application or datastore identity)
> - security on/off
> - mapping files
> - test data
> - list of test classes to be executed
>
> We started with the idea the test runner reads parameters from a 
> configuration file, e.g. an xml description. Some of the configuration 
> parameters are important for the build process and I see issues with 
> maven getting the info from the configuration file.
>
> I would like to propose to use properties files for the configuration 
> parameters such that maven can directly read and use these 
> configuration  properties.
>
> I propose to create a subdirectory called conf in the tck subproject. 
> It contains configuration files, one test configuration per file. The 
> file  has the standard properties format similar to the 
> project.properties file. The file defines a set of standard jdo tck 
> properties (the property names are just a proposal and subject to 
> change):
> jdo.tck.identitytype = application/datastore
> jdo.tck.security  = on/off
> jdo.tck.secutity.policyfile = <policyfilename>
> jdo.tck.mapping = <one or more .orm files>
> jdo.tck.testdata = <xml file with test data>
> jdo.tck.testclasses = <list of classnames>
>
> The project.properties file of the tck subproject defines a property 
> called jdo.tck.configuration pointing to one of the configuration files:
> jdo.tck.configuration = ${basedir}/conf/alltests.properties
> The user can specify the configuration to use by editing the file 
> project.properties or by setting a system property:
>   maven -Djdo.tck.configuration=conf/test.properties runtck
>
> The maven goal to run the tck for a specific configuration reads the 
> configuration properties from the file as specified by the property 
> jdo.tck.configuration:
>   <ant:property file="${jdo.tck.configuration}"/>
> This allows to adapt the classpath to include the enhanced pc classes 
> based on the identitytype.  Any configuration setting needed by the 
> TestRunner is passed as system property (e.g. the security policy 
> file) or as argument of the main method (e.g. the list of test classes 
> to be executed).
>
> Does this sound reasonable? Any feedback is appreciated.
>
> Regards Michael