[
http://jira.amdatu.org/jira/browse/AMDATU-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12345#comment-12345
]
Bram de Kruijff commented on AMDATU-487:
----------------------------------------
Looks good! Seems to aggregate nicely and thus include itest coverage. Some
notes on implementation/integration
1) For the aliased cmdline option to work you need to set plugingroups. Wont be
an issue when we tie it into the build though
{code}
<pluginGroups>
<pluginGroup>com.atlassian.maven.plugins</pluginGroup>
</pluginGroups>
{code}
2) The clover report is not integrated into the site (which would be nice). In
fact the site still shows the cobertura report which it inherits from the
parent.
3) Do we have a fail option? Do we want to set it at a minimal threshhold?
4) Old point above can easily be adressed when we tie it into the build for a
real test drive. Do you want to cover that in this issue?
> Improve / create testcoverage reporting
> ---------------------------------------
>
> Key: AMDATU-487
> URL: http://jira.amdatu.org/jira/browse/AMDATU-487
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Core
> Reporter: Bram de Kruijff
> Assignee: Bram de Kruijff
> Fix For: Sprint 2
>
>
> We want to be able to get an aggregate test coverage metric (unit +
> integration). This would allow us to set a reasonable minimal requirement:
> http://www.amdatu.org/confluence/display/Amdatu/Conventions+and+guidelines
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
