Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 26509 invoked from network); 17 Feb 2010 14:52:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2010 14:52:43 -0000 Received: (qmail 13329 invoked by uid 500); 17 Feb 2010 14:52:43 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 13297 invoked by uid 500); 17 Feb 2010 14:52:43 -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 13289 invoked by uid 99); 17 Feb 2010 14:52:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 14:52:43 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 14:52:36 +0000 Received: from [127.0.0.1] (bp-laptop.edgility.com [10.10.12.171]) by red.amberpoint.com (8.13.8/8.13.8) with ESMTP id o1HEqFot017483 for ; Wed, 17 Feb 2010 06:52:15 -0800 Message-ID: <4B7C029E.1070605@amberpoint.com> Date: Wed, 17 Feb 2010 06:52:14 -0800 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: JUnit-based concurrency tests References: <4B7AD4E6.1020703@sun.com> <4B7BEF6D.7050202@Sun.COM> In-Reply-To: <4B7BEF6D.7050202@Sun.COM> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > I'm not aware of any relevant existing base class in the Derby test > framework for running multi-threaded tests. I think that the classes and infrastructure in o.a.derbyTesting.perf.clients have much to offer. They are not JUnit test cases, but they have a lot of support for defining workloads, and managing threads, and tracking increments and timings. They are really more suited for running benchmarks, but hopefully there is a lot of re-usable code there for developing concurrent tests. thanks, bryan