Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 57316 invoked from network); 18 Oct 2007 11:36:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Oct 2007 11:36:43 -0000 Received: (qmail 69198 invoked by uid 500); 18 Oct 2007 11:36:30 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69161 invoked by uid 500); 18 Oct 2007 11:36:30 -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 69152 invoked by uid 99); 18 Oct 2007 11:36:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2007 04:36:30 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2007 11:36:42 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CD3B171420D for ; Thu, 18 Oct 2007 04:35:51 -0700 (PDT) Message-ID: <19401600.1192707351774.JavaMail.jira@brutus> Date: Thu, 18 Oct 2007 04:35:51 -0700 (PDT) From: "Ole Solberg (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2807) Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions. In-Reply-To: <13442226.1181641406119.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535893 ] Ole Solberg commented on DERBY-2807: ------------------------------------ 'org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite' (and 'org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.BLOBCLOB_CompatibilitySuite') are meant to be run via 'org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations' which sets up the environment for the desired combinations of servers and clients to be tested: 'CompatibilityCombinations' gets the compatibility suite to be run for each combination of Derby server and client from the file 'compatibilitytest.properties' in "user.dir". I.e. 'compatibilitytest.properties' must be created and put in your test execution directory. I then run the test like this export test=org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilityCombinations java -Xmx256m -Djava.security.policy= junit.textui.TestRunner ${test} 'compatibilitytest.properties' also specifies which combinations of jvm's should be used on the server and client sides. I am attaching an example 'compatibilitytest.properties' file. > Create a test for BlobClob compatibility on Derby server versions vs. Derby client versions. > -------------------------------------------------------------------------------------------- > > Key: DERBY-2807 > URL: https://issues.apache.org/jira/browse/DERBY-2807 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 10.3.1.4 > Reporter: Ole Solberg > Assignee: Ole Solberg > Priority: Minor > Attachments: derby-2807-v1.diff.txt > > > Run '..../tests/jdbcapi/BlobClob4BlobTest.java' in the 'java/testing/org/apache/derbyTesting/functionTests/tests/junitTests/compatibility/CompatibilityCombinations.java' framework to test combinations of Derby server versions vs. Derby client versions. The CompatibilityCombinations framework also allows varying the JVM version used on the server and client side. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.