Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of ole.ersoy@gmail.com designates
 64.233.166.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=HrxOu1GeJI0FYdDSFg37LCBOabZlp8QcQfb4JVu2cB80/0IMGLN8ktCeDC5aKYGcCmt5dj2IW2IpKObLeSBYOCMdwfxZVVhwpG767F2ka95o9vgMLyGzA0CLI5jIo++oFw/wdq8lsGeBlmqYL4GsSWQxtm32PAbs5lz9xnl/c3Y=
Message-ID: <466C32EE.3090103@gmail.com>
Date: Sun, 10 Jun 2007 12:20:46 -0500
From: Ole Ersoy <ole.ersoy@gmail.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: [Improvement] Standardized Test Setups for Projects
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hey Guys,

Should we have standardized test setups for projects?  This way, when 
creating a test and submitting it via JIRA, the test only contains the 
"Test", and uses the setup and from the pre-created Setup class.

For instance the self contained test I just submitted had all the 
connection and hot partitioning dependencies etc.  If there was a 
pre-created test projected for this, I would just check it out, update, 
and check back in.  Those without access to subversion, could just check 
out, create the test, attach to JIRA, and check back in...

Cheers,
- Ole