From: SourceForge.net <no...@so...> - 2010-07-31 14:04:11
|
Feature Requests item #3035416, was opened at 2010-07-27 11:58 Message generated for change (Comment added) made by paulbenedict You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=720018&aid=3035416&group_id=130558 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Vladimir Tsukur (flushdia) Assigned to: Nobody/Anonymous (nobody) Summary: Include Classes by Annotation Initial Comment: There is no way to include classes for analysis by class / interface annotations. Use case: part of the application code is public API. Each class / interface in public API is annotated with @PublicAPI. There is a need to collect code coverage statistics solely for public API code. ---------------------------------------------------------------------- Comment By: Paul Benedict (paulbenedict) Date: 2010-07-31 09:04 Message: Also, JavaDoc allows grouping via package wildcards. I wonder if a wildcard filter could be enabled since your public API should follow predictable naming pattern(s). ---------------------------------------------------------------------- Comment By: Paul Benedict (paulbenedict) Date: 2010-07-31 09:02 Message: An alternative solution is to introduce a @Category annotation ala JUnit 4.8. This annotation is an adhoc categorization. If Cobertura were to have something similar, you could then target one or several category combinations for your coverage report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=720018&aid=3035416&group_id=130558 |