Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14451 invoked from network); 1 Apr 2009 04:22:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Apr 2009 04:22:15 -0000 Received: (qmail 63235 invoked by uid 500); 1 Apr 2009 04:22:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 63165 invoked by uid 500); 1 Apr 2009 04:22:14 -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 63154 invoked by uid 99); 1 Apr 2009 04:22:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 04:22:14 +0000 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; Wed, 01 Apr 2009 04:22:13 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4C3D9234C003 for ; Tue, 31 Mar 2009 21:21:52 -0700 (PDT) Message-ID: <1238901743.1238559712298.JavaMail.jira@brutus> Date: Tue, 31 Mar 2009 21:21:52 -0700 (PDT) From: "Cheng Che Chen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4085) Improve testing of the in-memory back end In-Reply-To: <940596842.1236614690607.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694375#action_12694375 ] Cheng Che Chen commented on DERBY-4085: --------------------------------------- The test program uses the current time to initialize its random number generator, so every run is different. In the case of a failure, you'd have to note the random seed that it printed out at the beginning of the run, and then modify one line of the program to reuse that seed instead of using the current time, in order to repeat the run. > Improve testing of the in-memory back end > ----------------------------------------- > > Key: DERBY-4085 > URL: https://issues.apache.org/jira/browse/DERBY-4085 > Project: Derby > Issue Type: Sub-task > Components: Test > Affects Versions: 10.5.0.0 > Reporter: Kristian Waagan > Assignee: Kristian Waagan > Fix For: 10.6.0.0 > > Attachments: buildbreak.diff, derby-4085-1a-basic_tests.diff, derby-4085-1a-basic_tests.stat, derby-4085-1b-basic_tests.diff, derby-4085-2a-mog_func_test.diff, derby-4085-2a-mog_func_test.stat, derby-4085-3a-enable_in_suitesAll.diff, derby-4085-4a-improved_assertion_reporting.diff > > > The in-memory back end should be tested as part of the standard regression tests. > The following is a good start: > o simple create / boot test > o create in-memory db, backup, restore with default storage engine, modify, restore with createFrom into memory again > o add the functional test(s) written by Cheng > o more unit tests > On a longer term, we should consider to add the possibility to run all or a subset of the general regression tests with the in-memory back end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.