directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ole Ersoy <>
Subject Re: [Improvement] Standardized Test Setups for Projects
Date Sun, 10 Jun 2007 20:51:10 GMT
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.  
With the DAS I have 10 or so different setup classes each targeting a 
specific testing domain.  What I'll do first is document how these are 
being used, making it easy for others to extend the approach.  Then I'll 
submit it as a baseline example of one way  do it and we can see whether 
we like the approach.  I'm thinking each directory project should have 
an archetype with canned setups, and then contributors just add more as 
needed.  Thoughts?


- Ole

Alex Karasulu wrote:
> Take a look at this ...
> 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* < 
> <>> 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

View raw message