Alex Karasulu wrote:
On 6/10/07, *Ole Ersoy* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> 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* < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
> <mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> 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
>
>
>
