[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-2252) Coverage reports for JUnit tests
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Wed Jun 4 12:45:27 EDT 2008
[ http://jira.jboss.com/jira/browse/JBIDE-2252?page=all ]
Denis Golovin updated JBIDE-2252:
---------------------------------
Description:
Build should generate coverage report for JUnit tests
Coverage Report Trend is available here:
1. On JBossTools Build home page http://hudson.qa.jboss.com/hudson/job/JBossTools/
2. Coverage Report Trend Page http://hudson.qa.jboss.com/hudson/job/JBossTools//emma/
Coverage Report Statistics is available for each build. To see it:
1. Select a finished build
2. Then select Coverage Report link in the left menu
Coverage Report shows Class, Method, Block and Line coverage for:
1. All Packages
2. Particular Package
3. Particular Class
To adjust coverage testBuild.xml script should be modified in releng module.
Default rules to generate coverage report are:
<path id="tools.lib">
<fileset dir="${test-eclipse-root}/plugins">
<include name="org.jboss.*.jar" />
<include name="org.hibernate.*.jar" />
<include name="org.jboss.*/*.jar" />
<include name="org.hibernate.*/*.jar" />
<exclude name="*.test.*/*.jar" />
<exclude name="*.test.jar" />
<exclude name="*/freemarker*.jar" />
</fileset>
</path>
<emma enabled="true">
<instr metadatafile="${test-eclipse-root}/coverage.em" mode="overwrite" instrpathref="tools.lib">
<filter excludes="*.test.*" />
<filter excludes="*Test" />
<filter excludes="gnu.*" />
<filter excludes="org.dom4j.*" />
<filter excludes="org.jaxen.*" />
<filter excludes="freemarker.*"/>
<filter excludes="GetoptDemo"/>
</instr>
</emma>
To keep rules simple all jars should be moved from plug-in root to lib folder so
<exclude name="*.test.*/*.jar" />
<exclude name="*.test.jar" />
<exclude name="*/freemarker*.jar" />
and
<filter excludes="gnu.*" />
<filter excludes="org.dom4j.*" />
<filter excludes="org.jaxen.*" />
<filter excludes="freemarker.*"/>
<filter excludes="GetoptDemo"/>
can be romoved after that.
was:
Build should generate coverage report for JUnit tests
Coverage Report Trend is available here:
1. On JBossTools Build home page http://hudson.exadel.com/hudson/job/jboss-tools-nightly
2. Coverage Report Trend Page http://hudson.exadel.com/hudson/job/jboss-tools-nightly/emma/
Coverage Report Statistics is available for each build. To see it:
1. Select a finished build
2. Then select Coverage Report link in the left menu
Coverage Report shows Class, Method, Block and Line coverage for:
1. All Packages
2. Particular Package
3. Particular Class
To adjust coverage testBuild.xml script should be modified in releng module.
Default rules to generate coverage report are:
<path id="tools.lib">
<fileset dir="${test-eclipse-root}/plugins">
<include name="org.jboss.*.jar" />
<include name="org.hibernate.*.jar" />
<include name="org.jboss.*/*.jar" />
<include name="org.hibernate.*/*.jar" />
<exclude name="*.test.*/*.jar" />
<exclude name="*.test.jar" />
<exclude name="*/freemarker*.jar" />
</fileset>
</path>
<emma enabled="true">
<instr metadatafile="${test-eclipse-root}/coverage.em" mode="overwrite" instrpathref="tools.lib">
<filter excludes="*.test.*" />
<filter excludes="*Test" />
<filter excludes="gnu.*" />
<filter excludes="org.dom4j.*" />
<filter excludes="org.jaxen.*" />
<filter excludes="freemarker.*"/>
<filter excludes="GetoptDemo"/>
</instr>
</emma>
To keep rules simple all jars should be moved from plug-in root to lib folder so
<exclude name="*.test.*/*.jar" />
<exclude name="*.test.jar" />
<exclude name="*/freemarker*.jar" />
and
<filter excludes="gnu.*" />
<filter excludes="org.dom4j.*" />
<filter excludes="org.jaxen.*" />
<filter excludes="freemarker.*"/>
<filter excludes="GetoptDemo"/>
can be romoved after that.
My bad, links were updated
> Coverage reports for JUnit tests
> --------------------------------
>
> Key: JBIDE-2252
> URL: http://jira.jboss.com/jira/browse/JBIDE-2252
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: Build/Releng
> Affects Versions: 2.1.0.GA
> Reporter: Denis Golovin
> Assigned To: Denis Golovin
> Fix For: 2.1.x, 3.0.alpha
>
> Attachments: coverage-report-class.png, coverage-report-package.png, coverage-report-packages.png, coverage-tend-project.png, coverage-trend-page.png, jbosstools-emma-coverage.png
>
>
> Build should generate coverage report for JUnit tests
> Coverage Report Trend is available here:
> 1. On JBossTools Build home page http://hudson.qa.jboss.com/hudson/job/JBossTools/
> 2. Coverage Report Trend Page http://hudson.qa.jboss.com/hudson/job/JBossTools//emma/
> Coverage Report Statistics is available for each build. To see it:
> 1. Select a finished build
> 2. Then select Coverage Report link in the left menu
> Coverage Report shows Class, Method, Block and Line coverage for:
> 1. All Packages
> 2. Particular Package
> 3. Particular Class
> To adjust coverage testBuild.xml script should be modified in releng module.
> Default rules to generate coverage report are:
> <path id="tools.lib">
> <fileset dir="${test-eclipse-root}/plugins">
> <include name="org.jboss.*.jar" />
> <include name="org.hibernate.*.jar" />
> <include name="org.jboss.*/*.jar" />
> <include name="org.hibernate.*/*.jar" />
> <exclude name="*.test.*/*.jar" />
> <exclude name="*.test.jar" />
> <exclude name="*/freemarker*.jar" />
> </fileset>
> </path>
> <emma enabled="true">
> <instr metadatafile="${test-eclipse-root}/coverage.em" mode="overwrite" instrpathref="tools.lib">
> <filter excludes="*.test.*" />
> <filter excludes="*Test" />
> <filter excludes="gnu.*" />
> <filter excludes="org.dom4j.*" />
> <filter excludes="org.jaxen.*" />
> <filter excludes="freemarker.*"/>
> <filter excludes="GetoptDemo"/>
> </instr>
> </emma>
> To keep rules simple all jars should be moved from plug-in root to lib folder so
> <exclude name="*.test.*/*.jar" />
> <exclude name="*.test.jar" />
> <exclude name="*/freemarker*.jar" />
> and
> <filter excludes="gnu.*" />
> <filter excludes="org.dom4j.*" />
> <filter excludes="org.jaxen.*" />
> <filter excludes="freemarker.*"/>
> <filter excludes="GetoptDemo"/>
> can be romoved after that.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list