lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3005) Define Test Plan for 4.0
Date Fri, 14 Sep 2012 17:24:07 GMT


Robert Muir commented on LUCENE-3005:

Right, i think a lot of this is old news, its not perfect but we are closer.

As far as what Grant mentioned in the original thread: I think we've tried to automate this
as much
as possible in the it takes the actual generated artifacts and does a
of tests on them.

As i mentioned in the original thread, the worst part of the release process before was that
the code
wasn't releasable until someone cleaned it up: I think this is significantly better. We have
a lot
more checks in the build system: nitpicking over javadocs, 3rd party dependencies, license
etc, etc. And we run the as a weekly hudson job to ensure things like
are not broken.

In my opinion we should continue down this path, trying to ensure that our code is always
at any time from this kind of perspective, rather than adding manual steps.

I think the right way to do this is just like how we handle bugs in our code. If a problem
crops up
in e.g. packaging, don't just fix it, but also add a 'test' (code to smokeTestRelease or whatever)
that jenkins is continuously looking for it.

In my opinion most of the previous problems were all due to:
* not having tests (in this sense 'test' means testing packaging, licensing, etc)
* not having automated builds running those tests.

> Define Test Plan for 4.0
> ------------------------
>                 Key: LUCENE-3005
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Test
>    Affects Versions: 4.0-ALPHA
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.1
> Before we can release, we need a test plan that defines what a successful release candidate
must do to be accepted.
> Test plan should be written at
> See

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message