On 6/10/07, Ole Ersoy <firstname.lastname@example.org> 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.
I'm thinking each directory project should have
an archetype with canned setups, and then contributors just add more as
Hmmmm you mean providing a bunch of different test archetypes?
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?
> On 6/10/07, *Ole Ersoy* < email@example.com
> 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,
> and check back in. Those without access to subversion, could just
> out, create the test, attach to JIRA, and check back in...
> - Ole