You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Ole Ersoy <ol...@gmail.com> on 2007/06/10 19:20:46 UTC
[Improvement] Standardized Test Setups for Projects
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
Re: [Improvement] Standardized Test Setups for Projects
Posted by Ole Ersoy <ol...@gmail.com>.
Alex Karasulu wrote:
>
>
> On 6/10/07, *Ole Ersoy* <ole.ersoy@gmail.com
> <ma...@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
> <ma...@gmail.com>
> > <mailto: ole.ersoy@gmail.com <ma...@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
> >
> >
> >
>
>
Re: [Improvement] Standardized Test Setups for Projects
Posted by Alex Karasulu <ak...@apache.org>.
On 6/10/07, Ole Ersoy <ol...@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
> > <ma...@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
> >
> >
> >
>
>
Re: [Improvement] Standardized Test Setups for Projects
Posted by Ole Ersoy <ol...@gmail.com>.
>
> well, if you can spend an hour looking at tests done in core-unit and
> in server-unit, it would also help you a lot. Can you do that? Maybe
> your approach plus what we have can overlap a lot, and you can spare a
> lot of time, and bring the tests to a new level of usability !
>
Sure - I'll try to make as much use out of what we have already as
possible so the view presented is unified.
Cheers,
- Ole
Re: [Improvement] Standardized Test Setups for Projects
Posted by Emmanuel Lecharny <el...@apache.org>.
Ole Ersoy a écrit :
> 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.
yeah, you are plain right.
> So we could start with an archetype like that and just document how to
> go about using it and what it contains.
We have done some kind of standardization for tests in 1.0, but it'sd :
1) not perfect
2) not documented
3) slow in 1.5 for many reasons (mainly because we are initializing the
server for each single test)
> 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.
ok, just perfet !
> 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?
well, if you can spend an hour looking at tests done in core-unit and in
server-unit, it would also help you a lot. Can you do that? Maybe your
approach plus what we have can overlap a lot, and you can spare a lot of
time, and bring the tests to a new level of usability !
Thanks a lot, Ole! This is very valuable !
Emmanuel
Re: [Improvement] Standardized Test Setups for Projects
Posted by Ole Ersoy <ol...@gmail.com>.
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?
Thoughts?
Cheers,
- 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
> <ma...@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
>
>
>
Re: [Improvement] Standardized Test Setups for Projects
Posted by Alex Karasulu <ak...@apache.org>.
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 <ol...@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
>
>
>