[jbosstools-issues] [JBoss JIRA] (JBIDE-13155) Links to code coverage data file jacoco.exec are broken for some components
[
https://issues.jboss.org/browse/JBIDE-13155?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-13155:
----------------------------------------
[~dgolovin]: From developer point of view I want to be able to run
individual test plugin and then review coverage report
Ok, you can already do this.
{code}
$ mvn verify -f tests/my.magic.test/pom.xml
{code}
and then enjoy your target/jacoco.exec in EclEmma
[~dgolovin]: It doesn't make sense provide coverage for the whole
component build only, because it would required to run whole component tests to see
coverage report for individual plugin.
Coverage is here to spot which pieces of code are not covered and should have more testing
love. Having a component-wide grain of analysis allows to find out where to put efforts on
the whole component. Although I don't use them extensively, I feel these reports are
(or will be) useful.
[~nickboldt]: Fixed in 4 x 2 jobs (stable_branch and trunk) for
javaee, server, central-maven-examples and base
The jacoco.exec are not archived, so we only keep the jacoco.exec of the latest build. I
tend to think that as long as we don't have complaints, it's not bad.
Links to code coverage data file jacoco.exec are broken for some
components
---------------------------------------------------------------------------
Key: JBIDE-13155
URL: https://issues.jboss.org/browse/JBIDE-13155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.CR1
Reporter: Vlado Pakan
Assignee: Nick Boldt
Fix For: 4.0.0.CR1
jacoco.exec files are not available for these modules on Jenkins jobs for JBT 4.0 stable
branch: base, birt, central-maven-examples, javaee, server.
Each job has a link to jacoco.exec file but while navigating to this link within jobs of
modules listed above "HTTP Status 404 -" error web page is displayed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira