Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 8 Feb 2011 17:03:57 +0000 (UTC)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <745863569.2719.1297184637981.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Closed: (DERBY-1116) Define a minimal acceptance test suite
 for checkins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren closed DERBY-1116.
-------------------------------------

    Resolution: Won't Fix

Closing as discussed.

> Define a minimal acceptance test suite for checkins
> ---------------------------------------------------
>
>                 Key: DERBY-1116
>                 URL: https://issues.apache.org/jira/browse/DERBY-1116
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: David Van Couvering
>            Priority: Minor
>
> Now that we have an excellent notification system for tinderbox/nightly regression failures, I would like to suggest that we reduce the size of the test suite being run prior to checkin.   I am not sure what should be in such a minimal test, but in particular I would like to remove things such as the stress test and generally reduce the number of tests being run for each subsystem/area of code.
> As an example of how derbyall currently affects my productivity, I was running derbyall on my machine starting at 2pm, and by evening it was still running.  At 9pm my machine was accidentally powered down, and this morning I am restarting the test run.
> I have been tempted (and acted on such temptation) in the past to run a smaller set of tests, only to find out that I have blocked others who are running derbyall prior to checkin.  For this reason, we need to define a minimal acceptance test (MATS) that we all agree to run prior to checkin.
> One could argue that you can run your tests on another machine and thus reduce productivity, but we can't assume everybody in the community has nice big test servers to run their tests on.
> If there are no objections, I can take a first pass at defining what this test suite should look like, but I suspect many others in the community have strong opinions about this and may even wish to volunteer to do this definition themselves (for example, some of you who may be working in the QA division in some of our Big Companies :) ).

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira