Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 73108 invoked from network); 19 Jul 2006 16:11:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Jul 2006 16:11:40 -0000 Received: (qmail 52201 invoked by uid 500); 19 Jul 2006 16:11:39 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 52182 invoked by uid 500); 19 Jul 2006 16:11:39 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 52171 invoked by uid 99); 19 Jul 2006 16:11:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2006 09:11:39 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Jul 2006 09:11:38 -0700 Received: from ajax.apache.org (localhost [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id D20376ACA9 for ; Wed, 19 Jul 2006 17:11:17 +0100 (BST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: derby-commits@db.apache.org Date: Wed, 19 Jul 2006 16:11:17 -0000 Message-ID: <20060719161117.7110.90377@ajax.apache.org> Subject: [Db-derby Wiki] Update of "TenTwoApplicationTesting" by KatheyMarsden X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Dear Wiki user, You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification. The following page has been changed by KatheyMarsden: http://wiki.apache.org/db-derby/TenTwoApplicationTesting ------------------------------------------------------------------------------ Derby's FowardCompatibility goal is to allow any application written against the public interfaces of an older version of Derby to run, without any changes, against a newer version of Derby. Any incompatible changes should be a concious decision and be recorded in Jira with the "Existing Application Impact" checkbox. - To verify this is true for the 10.2 release, please test applications that use Derby and make sure we have provided as seamless an upgrade as possible for existing applications. Try your own application or some other application that you use. The table below has a few examples. See [http://db.apache.org/derby/integrate/index.html Derby Resources] and UsesOfDerby for more possiblities. + To verify this is true for the 10.2 release and to help ensure you don't have problems upgrading *after* the release, please test applications that use Derby and make sure we have provided as seamless an upgrade as possible for existing applications. Try your own application or some other application that uses Derby. The table below has a few examples. See [http://db.apache.org/derby/integrate/index.html Derby Resources] and UsesOfDerby for more possiblities. + == How to do Application Testing for 10.2 == + 1. Download the latest snapshot from [http://db.apache.org/derby/derby_downloads.html Derby downloads] or the latest 10.2 unofficial build by following the link the same page. (Check test results first if using the unofficial build.) + 2. Try an application. Perform a tutorial, do formal regression tests or just do something ad hoc. Note: There is no in-place upgrade to/from 10.2, so typically you want to make a new database from scratch. + - Please record your results below. In the comments section indicate if you saw any performance changes if relevant and if you found intentional changes that were not marked properly in Jira. Click [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&customfield_12310090=Existing+Application+Impact&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESCrg/jira/secure/ConfigureReport.jspa?filterid=12310892 here] for known changes that might affect existing applications + 3. Record your results below. In the comments section indicate if you saw any performance changes and if you found intentional changes that were not marked properly in Jira. Click [http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&customfield_12310090=Existing+Application+Impact&sorter/field=issuekey&sorter/order=ASC&sorter/field=updated&sorter/order=DESC&sorter/field=priority&sorter/order=DESCrg/jira/secure/ConfigureReport.jspa?filterid=12310892 here] for known changes that might affect existing applications. + ||'''Name of Application'''|| '''Tests Performed'''|| '''Tester'''||'''Bugs Filed'''||'''Comments'''|| ||DDLUtils|| [http://db.apache.org/derby/integrate/db_ddlutils.html DDLUtils tutorial]|| || || ||