You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Santhosh Kumar Edukulla (JIRA)" <ji...@apache.org> on 2013/10/29 12:36:48 UTC

[jira] [Updated] (CLOUDSTACK-4986) Analysing and implementing Code Coverage for Integration Tests

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Santhosh Kumar Edukulla updated CLOUDSTACK-4986:
------------------------------------------------

    Summary: Analysing and implementing Code Coverage for Integration Tests  (was: Doing Code Coverage for Integration Tests)

> Analysing and implementing Code Coverage for Integration Tests
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4986
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4986
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Infra
>            Reporter: Santhosh Kumar Edukulla
>            Assignee: Santhosh Kumar Edukulla
>
> Currently, we have facility to  use and run sonar for analyzing  code coverage numbers for CS using unit tests. We need to enhance it to support analysis for integration tests coverage as well. Basically, this will give coverage numbers for both integration and unit tests.
> 1.It seems we already have a code coverage numbers using sonar as below. It currently shows only the numbers for unit tests.
> https://analysis.apache.org/dashboard/index/100206
> 2. The below link has an explanation for using it for both for integration and unit tests.
> http://docs.codehaus.org/display/SONAR/Code+Coverage+by+Integration+Tests+for+Java+Project
> 3. Many links suggests it has good decision coverage facility compared to other coverage tools.
> http://onlysoftware.wordpress.com/2012/12/19/code-coverage-tools-jacoco-cobertura-emma-comparison-in-sonar/
> Logging this bug to track this effort and changes.



--
This message was sent by Atlassian JIRA
(v6.1#6144)