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 akarasulu@gmail.com designates
 64.233.162.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=Pn1cgURJcJ7wIZqiAJ2dtasEPsteBQdpYLWODhVtj+R6VT524SvGOf+pjJRFmtXj6UpX+MWfV/7bZNKMp6AM3SfonEguqlLhX++PRUtf4A9lbKFrtTl8r6dHEO/d2gpuQ3Du3bSeVPC3//N8aeELDbRAfNABL1j9w7xyUgxVlp4=
Message-ID: <a32f6b020706101026o4aee1581pe6adc268385ecd19@mail.gmail.com>
Date: Sun, 10 Jun 2007 19:26:12 +0200
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: [Improvement] Standardized Test Setups for Projects
In-Reply-To: <466C32EE.3090103@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_56091_20754109.1181496372425"
References: <466C32EE.3090103@gmail.com>

------=_Part_56091_20754109.1181496372425
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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> 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
>
>
>

------=_Part_56091_20754109.1181496372425
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Take a look at this ...<br><br><a href="https://svn.apache.org/repos/asf/directory/apacheds/branches/1.0/testcase-archetype/">https://svn.apache.org/repos/asf/directory/apacheds/branches/1.0/testcase-archetype/</a><br><br>
We need the same thing for 1.5 which does not have it yet.&nbsp; Want to whip it together?<br><br>Alex<br><br><div><span class="gmail_quote">On 6/10/07, <b class="gmail_sendername">Ole Ersoy</b> &lt;<a href="mailto:ole.ersoy@gmail.com">
ole.ersoy@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hey Guys,<br><br>Should we have standardized test setups for projects?&nbsp;&nbsp;This way, when
<br>creating a test and submitting it via JIRA, the test only contains the<br>&quot;Test&quot;, and uses the setup and from the pre-created Setup class.<br><br>For instance the self contained test I just submitted had all the
<br>connection and hot partitioning dependencies etc.&nbsp;&nbsp;If there was a<br>pre-created test projected for this, I would just check it out, update,<br>and check back in.&nbsp;&nbsp;Those without access to subversion, could just check<br>
out, create the test, attach to JIRA, and check back in...<br><br>Cheers,<br>- Ole<br><br><br></blockquote></div><br>

------=_Part_56091_20754109.1181496372425--