Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49081 invoked from network); 3 Nov 2006 02:32:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Nov 2006 02:32:50 -0000 Received: (qmail 16496 invoked by uid 500); 3 Nov 2006 02:33:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16472 invoked by uid 500); 3 Nov 2006 02:33:01 -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 16463 invoked by uid 99); 3 Nov 2006 02:33:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 18:33:01 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2006 18:32:48 -0800 Received: from [127.0.0.1] (bp-laptop.edgility.com [10.10.11.64]) by red.amberpoint.com (8.12.11/8.12.11) with ESMTP id kA32WOwM024588 for ; Thu, 2 Nov 2006 18:32:24 -0800 (PST) Message-ID: <454AAA38.2060302@amberpoint.com> Date: Thu, 02 Nov 2006 18:32:24 -0800 From: Bryan Pendleton User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Running tests both with and without sqlAuthorization=true Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org During the review for DERBY-1490, several reviewers noted that it would be useful to be able to run various tests in two configurations: - with sqlAuthorization=true - with sqlAuthorization=false A good example of this is the test suite lang/altertable.sql, which currently runs with sqlAuthorization=true, but since there are a variety of different code paths for both sqlAuthorization configurations, it would be nice if this test suite also ran with sqlAuthorization=false. How does the new JUnit framework handle this situation? Will this problem "go away" when all the lang/*.sql tests have been converted to JUnit? thanks, bryan