You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2018/02/11 18:19:00 UTC
[jira] [Updated] (LUCENE-8170) Improve OpenClover reports (separate
test from production code)
[ https://issues.apache.org/jira/browse/LUCENE-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-8170:
----------------------------------
Attachment: LUCENE-8170.patch
> Improve OpenClover reports (separate test from production code)
> ---------------------------------------------------------------
>
> Key: LUCENE-8170
> URL: https://issues.apache.org/jira/browse/LUCENE-8170
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/test
> Reporter: Uwe Schindler
> Assignee: Uwe Schindler
> Priority: Major
> Fix For: master (8.0), 7.3
>
> Attachments: LUCENE-8170.patch
>
>
> Currently the Clover reports mix production and test code. This is due to a misunderstanding (by bad documentation). The testsources in clover-setup are treated different than at reporting time. In clover setup they are only used to figure out where tests could possibly be, but final decision is done on the file name and annotations. All code inside testsources of cloversetup thats not a real test is treated as application class. So we see our test-framework classes and utility classes between our production code in the report.
> To fix this, the clover-report task must get a fileset (unfortunately, with same name like clover-setup to make it more confusing) that selects all java files which are part of test code (testcases and utility code).
> Once I figured this out this was easy to fix!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org