Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 23812 invoked from network); 24 Nov 2005 13:07:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 24 Nov 2005 13:07:05 -0000 Received: (qmail 70478 invoked by uid 500); 24 Nov 2005 13:07:05 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Delivered-To: moderator for jdo-dev@db.apache.org Received: (qmail 64458 invoked by uid 99); 24 Nov 2005 08:37:04 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) From: Andy Jefferson To: jdo-dev@db.apache.org Subject: TCK : structuring Date: Thu, 24 Nov 2005 09:36:36 +0100 User-Agent: KMail/1.7.2 Organization: JPOX MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511240936.37330.andy@jpox.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Has any thought been given to splitting the "alltests.conf" up into modules? so we could have for example pmf.conf pm.conf jdoql.conf sql.conf etc with each configuration testing the functionality of that part of JDO. The number of tests in alltests.conf (545) is becoming large, and the name of a test doesn't necessarily tell me what it is testing (e.g we have ShapeOfResult tests for JDOQL *and* SQL and it isn't obvious from viewing the listing which is which). At least splitting the JDOQL and SQL tests out into their own configuration would make sense (to me). -- Andy