On Thu, Jul 30, 2009 at 6:14 AM, Uwe Schindler<u...@thetaphi.de> wrote:
> I for got to mention: <testsources> only works for clover 2.x this is why I
> updated. The update was simple, I only had to change one line in
> common-build.xml and add the testsources tag with the current
> junit.include/exclude and ASCIIFoldingFilter exclusions.
Great.
> Addition of test-tag is more complicated, as the source directory names are
> not so simple to find and are not available at the time of setup-clover
> task.
>
> I will post a patch after the complete ant test has run here in complete
> (will take some time).
OK.
>> Can't we see coverage of core code, by both the current unit tests and
>> the back-compat unit tests?
>
> We would see, my intention is to only instrument the coe/contrib tests to
> find out places were the test does not cover all code, but a previous test
> from test-tag had done.
I see; that would be an interesting report.
> In ideal world all test of current trunk should test
> all code without the help of test-tag.
I'm not sure that's the ideal we should aim for.
EG, if we make some API change on trunk, marking the old API
deprecated, shouldn't we at that point move the existing tests over to
the new API, and then "rely" on the back-compat tests to invoke
("cover", as reported by Clover) the deprecated API?
Or, should we always leave some trunk tests using the deprecated APIs?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
