Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 10297 invoked from network); 22 Feb 2008 23:38:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Feb 2008 23:38:03 -0000 Received: (qmail 88899 invoked by uid 500); 22 Feb 2008 23:37:58 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 88861 invoked by uid 500); 22 Feb 2008 23:37:58 -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 88852 invoked by uid 99); 22 Feb 2008 23:37:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2008 15:37:58 -0800 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; Fri, 22 Feb 2008 23:37:19 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6921E234C010 for ; Fri, 22 Feb 2008 15:37:19 -0800 (PST) Message-ID: <1115714464.1203723439429.JavaMail.jira@brutus> Date: Fri, 22 Feb 2008 15:37:19 -0800 (PST) From: "Myrna van Lunteren (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Issue Comment Edited: (DERBY-2667) Create more robust junit TestRunner for running derby tests In-Reply-To: <21516908.1179464776126.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-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571270#action_12571270 ] myrna edited comment on DERBY-2667 at 2/22/08 3:36 PM: -------------------------------------------------------------------- Thanks Manjula, I like the latest patch. I committed patch DERBY-2667_diff_02_21.txt with revision 630077. Probably superfluous, but, I do want to point out that the TestConfiguration.getFailureFolder creates a 'fail' folder, and all directories underneath (fail///). This means, that if you run a subsequent failing fixture test in the same top level directory, previous derby.logs will be overwritten, and also, old run's fail directories won't get cleaned out. was (Author: myrna): Thanks Manjula, I like the latest patch. I committed patch DERBY-2667_diff_02_21.txt with revision 63007. Probably superfluous, but, I do want to point out that the TestConfiguration.getFailureFolder creates a 'fail' folder, and all directories underneath (fail///). This means, that if you run a subsequent failing fixture test in the same top level directory, previous derby.logs will be overwritten, and also, old run's fail directories won't get cleaned out. > Create more robust junit TestRunner for running derby tests > ------------------------------------------------------------ > > Key: DERBY-2667 > URL: https://issues.apache.org/jira/browse/DERBY-2667 > Project: Derby > Issue Type: Improvement > Components: Test > Affects Versions: 10.3.1.4 > Reporter: Kathey Marsden > Priority: Minor > Attachments: DERBY-2667_diff_02_06.txt, DERBY-2667_diff_02_15.txt, DERBY-2667_diff_02_21.txt, DERBY-2667_diff_2_19.txt, DERBY-2667_stat_02_06.txt, DERBY-2667_stat_02_15.txt, DERBY-2667_stat_02_19.txt, DERBY-2667_stat_02_21.txt, JUnitMethodTrace.diff.txt, JUnitMethodTrace_Extra.diff.txt, MemRunner.java, TimeRunner.java > > > Provide a more full featured TestRunner for Derby testing. > junit.textui.TestRunner is not very robust. It does not for example print the tests as they run or print chained exceptions, create separate files for the full report and just failures. It would be great to have a standardized TestRunner that everyone uses. Perhaps someone already has one that they would like to contribute as a starter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.