directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <akaras...@apache.org>
Subject Re: [Improvement] Standardized Test Setups for Projects
Date Sun, 10 Jun 2007 21:17:44 GMT
On 6/10/07, Ole Ersoy <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

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?

Alex

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

Mime
View raw message