Adding "testpackage" to common-build.xml

[Shai Erera <se...@gmail.com>]

Hi

I noticed that one can define "testcase" to execute just one test class,
which is convenient. However, I didn't notice any equivalent for testing a
whole package. Lately, when handling all those search issues, I often wanted
to run all the tests in o.a.l.search and just them, but couldn't so I either
ran a single test class when it was obvious (like TestSort) or the
"test-core" when it was less obvious (like changes to Collector, or
BooleanScorer).

I wrote a simple patch which adds this capability to common-build.xml. I
would like to confirm first that you agree to add this change and that I
didn't miss it and this capability exists elsewhere already.

Shai

Re: Adding "testpackage" to common-build.xml

[Shai Erera <se...@gmail.com>]

ok then I'll open an issue and post the patch. You can review it and give it
a try

Shai

On Mon, Apr 27, 2009 at 2:10 PM, Michael McCandless <
lucene@mikemccandless.com> wrote:

> This sounds like a great change!  It would also allow us to test the
> other (index, store, etc.) packages too?
>
> I don't think this is possible today, though I'm no expert with ant so
> it's entirely possible I've missed it.
>
> Presumably once we "modularize", then the "module" would be the
> natural unit for testing (but it seems like this will be a ways
> off...).
>
> Mike
>
> On Mon, Apr 27, 2009 at 7:01 AM, Shai Erera <se...@gmail.com> wrote:
> > Hi
> >
> > I noticed that one can define "testcase" to execute just one test class,
> > which is convenient. However, I didn't notice any equivalent for testing
> a
> > whole package. Lately, when handling all those search issues, I often
> wanted
> > to run all the tests in o.a.l.search and just them, but couldn't so I
> either
> > ran a single test class when it was obvious (like TestSort) or the
> > "test-core" when it was less obvious (like changes to Collector, or
> > BooleanScorer).
> >
> > I wrote a simple patch which adds this capability to common-build.xml. I
> > would like to confirm first that you agree to add this change and that I
> > didn't miss it and this capability exists elsewhere already.
> >
> > Shai
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>

Re: Adding "testpackage" to common-build.xml

[Michael McCandless <lu...@mikemccandless.com>]

This sounds like a great change!  It would also allow us to test the
other (index, store, etc.) packages too?

I don't think this is possible today, though I'm no expert with ant so
it's entirely possible I've missed it.

Presumably once we "modularize", then the "module" would be the
natural unit for testing (but it seems like this will be a ways
off...).

Mike

On Mon, Apr 27, 2009 at 7:01 AM, Shai Erera <se...@gmail.com> wrote:
> Hi
>
> I noticed that one can define "testcase" to execute just one test class,
> which is convenient. However, I didn't notice any equivalent for testing a
> whole package. Lately, when handling all those search issues, I often wanted
> to run all the tests in o.a.l.search and just them, but couldn't so I either
> ran a single test class when it was obvious (like TestSort) or the
> "test-core" when it was less obvious (like changes to Collector, or
> BooleanScorer).
>
> I wrote a simple patch which adds this capability to common-build.xml. I
> would like to confirm first that you agree to add this change and that I
> didn't miss it and this capability exists elsewhere already.
>
> Shai
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org