[ http://jira.jboss.com/jira/browse/JBIDE-2252?page=all ] Denis Golovin updated JBIDE-2252: --------------------------------- Attachment: jbosstools-emma-coverage.png I played a bit with emma and eclemma and find the way to create coverage report for JBossTool. So I used pure emma for that because of lack of means to filter packages that should be used for coverage report generation in eclemma. Ecleemma always shows report for all loaded classes and I couldn't find a way to include in report only JBossTools classes. It is really simple, but I have no commiter rights to releng anymore. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-2252?page=all ] Denis Golovin updated JBIDE-2252: --------------------------------- Comment: was deleted -- 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

[ 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.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. was:Build should generate coverage report for JUnit tests -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-2252?page=all ] Denis Golovin updated JBIDE-2252: --------------------------------- Attachment: coverage-tend-project.png coverage-trend-page.png -- 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

[ 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 -- 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