[jbossts-issues] [JBoss JIRA] (JBTM-1777) Set up a CI job to run codeCoverage tests

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Fri Jun 14 05:27:55 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson resolved JBTM-1777.
---------------------------------

    Resolution: Done


Reports now available here:
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/lastSuccessfulBuild/artifact/qa/testoutput/emma/coverage.html

and:
http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/lastSuccessfulBuild/artifact/
                
> Set up a CI job to run codeCoverage tests
> -----------------------------------------
>
>                 Key: JBTM-1777
>                 URL: https://issues.jboss.org/browse/JBTM-1777
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.M4
>
>
> We do not currently run automated code coverage report generation in CI. It would be worth setting up a job to run this weekly. I imagine all the tests will need to be run on the same node unless we get aggregation to work and that is why I am thinking it will be a new job rather than a modification of the existing job (which runs different parts of the build in parallel on different nodes).
> If we were to get aggregation to work it may be possible (if it doesn't add much time to the build) to run this profile in CI.
> We should also determine suitable coverage metrics to aim for.

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


More information about the jbossts-issues mailing list