Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 49313 invoked from network); 5 Jun 2008 17:12:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Jun 2008 17:12:40 -0000 Received: (qmail 16969 invoked by uid 500); 5 Jun 2008 17:12:09 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 16940 invoked by uid 500); 5 Jun 2008 17:12:09 -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 16865 invoked by uid 99); 5 Jun 2008 17:12:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 10:12:08 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2008 17:11:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 0E168234C12F for ; Thu, 5 Jun 2008 10:11:45 -0700 (PDT) Message-ID: <2078772950.1212685905056.JavaMail.jira@brutus> Date: Thu, 5 Jun 2008 10:11:45 -0700 (PDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3711) convert store/aes.sql to junit test & add unrestricted test cases. In-Reply-To: <687066723.1212618465011.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-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602714#action_12602714 ] Kathey Marsden commented on DERBY-3711: --------------------------------------- Myrna asked. >Would it be useful/ok to have a message print to the console as a warning (if larger key sizes are skipped)? I wouldn't mind a message, but I think it is not the norm for tests we skip because there is not support, so maybe others have different opinions. > convert store/aes.sql to junit test & add unrestricted test cases. > ------------------------------------------------------------------ > > Key: DERBY-3711 > URL: https://issues.apache.org/jira/browse/DERBY-3711 > Project: Derby > Issue Type: Task > Components: Test > Reporter: Myrna van Lunteren > Assignee: Myrna van Lunteren > Priority: Minor > > The store/aes.sql test can, because it's a master-based test, only test what's guaranteed available, i.e. only the encryptionKeyLength=128. > If it were a junit test, we could make it ignore the expected failures if the larger key sizes weren't supported, but test otherwise. > Having a junit test doesn't guarantee the test would get executed, of course, but at least the test would exist. > Would it be useful/ok to have a message print to the console as a warning? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.