From torque-dev-return-7538-apmail-db-torque-dev-archive=db.apache.org@db.apache.org Mon Nov 27 19:04:04 2006 Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 36208 invoked from network); 27 Nov 2006 19:04:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Nov 2006 19:04:04 -0000 Received: (qmail 93157 invoked by uid 500); 27 Nov 2006 19:04:13 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 93142 invoked by uid 500); 27 Nov 2006 19:04:13 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 93131 invoked by uid 99); 27 Nov 2006 19:04:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 11:04:13 -0800 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of Greg.Monroe@dukece.com designates 65.112.55.73 as permitted sender) Received: from [65.112.55.73] (HELO mail.dukece.com) (65.112.55.73) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 11:04:01 -0800 Received: from dukece-mail3.dukece.com ([192.168.1.222]) by mail.dukece.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 27 Nov 2006 14:04:12 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C71256.BF3415FC" Subject: Opinions on adding new -D option to test-project cmd line Date: Mon, 27 Nov 2006 14:03:38 -0500 Message-ID: <8F5843B903F59D4C8C6806BB49A3911901FA2113@dukece-mail3.dukece.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Opinions on adding new -D option to test-project cmd line Thread-Index: AccSVr8R0cInM7xnRYWRZ5CJhF5YdA== From: "Greg Monroe" To: "Apache Torque Developers List" X-OriginalArrivalTime: 27 Nov 2006 19:04:12.0671 (UTC) FILETIME=[D36900F0:01C71256] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C71256.BF3415FC Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I've been working on a modification to the Test-project=20 run scripts to make it easier to test with the various option combinations. See: =20 http://mail-archives.apache.org/mod_mbox/db-torque-dev/200611.mbox/%3c8F 5843B903F59D4C8C6806BB49A3911901E92738@dukece-mail3.dukece.com%3e =20 Before I get too far into working on this, I thought I'd=20 poll folks to see if the basic design is OK. =20 The goal here is to be able to do test runs using a=20 combination of locally defined DB settings (e.g., the=20 existing profiles) and a set of pre-defined Torque=20 Generation options. This way you just define your=20 local test DB info once. Then run the test-project=20 against the combinations of options sets you need. =20 The best way to do this is to expand on how the=20 existing test-project uses tags in it's=20 project.xml file to work. E.g., all test runs require the command line option: =20 -Dtorque.test.profile=3D =20 which causes the profile's project.properties to be added to the test-project's project.properties. =20 The change I'm proposing (and have a proof of principal version done), is to modify the chain so that=20 the test-project extends a generation option set which extends the db profile set. This means doing a test run=20 would now require a command line with an additional=20 option. E.g.: =20 maven -Dtorque.test.profile=3Dmysql -Dtorque.test.options=3Ddb-test1 =20 Where db-test1 is be a directory located under a=20 run-options directory (like the profile directory)=20 containing a project.properties file with a set of=20 Torque generation options and a simple project.xml file. =20 The reason to do it this way is that project.properties are immutable, i.e. once set they can not be changed. So, having the run options low in the extends chain ensures you are testing what you think you are and not some leftover settings in a local DB profile. =20 I'm planning on created the sets needed to do all the option combination specified in the dev e-mail referenced=20 (plus documentations, etc). =20 For quick development testing, this should be a minor=20 change. Just update whatever method you use in testing mods to include your favorite option set(s). (FWIW, the two db specific tests described probably cover 80-90%=20 of possible problems). If you have a personal favorite set=20 of options, just create your own run-options directory. =20 To validate a patch with the SVN head, just check out a sandbox version of torque, apply the patch, copy in=20 your local db profiles, and run the appropriate set of tests. This would be very easy to script the run=20 process (and maybe eventually do a results roll up). =20 Thoughts? Other ways to do this? Enhancements? etc. =20 Greg Greg Monroe (919)680-5050 C&IS Solutions Team Lead Duke Corporate Education, Inc. 333 Liggett St. Durham, NC 27701 =20 Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are = confidential communication or may otherwise be privileged or = confidential and are intended solely for the individual or entity to = whom they are addressed. If you are not the intended recipient you may = not rely on the contents of this email or any attachments, and we ask = that you please not read, copy or retransmit this communication, but = reply to the sender and destroy the email, its contents, and all copies = thereof immediately. Any unauthorized dissemination, distribution or = copying of this communication is strictly prohibited. ------_=_NextPart_001_01C71256.BF3415FC--