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.178 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:references:in-reply-to:content-type:content-transfer-encoding;
        b=KulH3vLBUyVjh9DJ0unkUar1R46z/Yrnwsffpb5En2I04Dp0oaPiBOdcGm9tNV7CJwWbVFRtFDQSkkvpJWtwZS3Iuyxx6qODbC2750X7AJa4B1+pmg6pNX9tlO17vuarULjYKUWKD3jfhjFBaNek59xmeAm1VJbIb20PQSQohhI=
Message-ID: <466C717A.7010301@gmail.com>
Date: Sun, 10 Jun 2007 16:47:38 -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: Re: [Improvement] Standardized Test Setups for Projects
References: <466C32EE.3090103@gmail.com>
	 <a32f6b020706101026o4aee1581pe6adc268385ecd19@mail.gmail.com>
	 <466C643E.7000306@gmail.com>
 <a32f6b020706101417g7407afa1of0ac56f79e30211e@mail.gmail.com>
In-Reply-To: <a32f6b020706101417g7407afa1of0ac56f79e30211e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Alex Karasulu wrote:
>
>
> On 6/10/07, *Ole Ersoy* <ole.ersoy@gmail.com 
> <mailto:ole.ersoy@gmail.com>> wrote:
>
>     I think it's really important to standardize the process around the
>     submission of tests, with a focus on minimizing the effort for
>     submission and integration.  So we could start with an archetype like
>     that and just document how to go about using it and what it contains. 
>
>
> You mean like this?
>
>      http://cwiki.apache.org/confluence/display/DIRxSRVx10/Reporting+Bugs
Lookee Here :-)  Yes - Like that - Thanks.   I'll make sure I work with 
this.
>
>     I'm thinking each directory project should have
>     an archetype with canned setups, and then contributors just add
>     more as
>     needed.  Thoughts?
>
>
> Hmmmm you mean providing a bunch of different test archetypes?
Yes.  It's an idea.  I'm just imagining that some setups for LS, 
Triplesec, etc. might be somewhat unrelated and keeping the 
documentation focus on separate archetypes will make it easier to manage 
and improve the test process around each project.
>
> Alex
Ole


>
>     Alex Karasulu wrote:
>     > Take a look at this ...
>     >
>     >
>     https://svn.apache.org/repos/asf/directory/apacheds/branches/1.0/testcase-archetype/
>     >
>     > We need the same thing for 1.5 which does not have it yet.  Want to
>     > whip it together?
>     >
>     > Alex
>     >
>     > On 6/10/07, *Ole Ersoy* < ole.ersoy@gmail.com
>     <mailto:ole.ersoy@gmail.com>
>     > <mailto: ole.ersoy@gmail.com <mailto:ole.ersoy@gmail.com>>> wrote:
>     >
>     >     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
>     >
>     >
>     >
>
>