Re: [Dev] Testing Jacoco based code coverage genration

2015-05-25 Thread Nuwan Wimalasekara
Hi Ramith, You can find the documentation from[1] [1] https://docs.google.com/document/d/1pMJGdRH4Kmc4J3rYzgnpGlR5AnSeoC4QL9gMX9tUhYs/edit#heading=h.yemie7ivahbz Thanks, Nuwanw On Sat, May 23, 2015 at 4:18 PM, Ramith Jayasinghe wrote: > do we have any documentation on this? > > On Wed, May 13,

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-23 Thread Ramith Jayasinghe
do we have any documentation on this? On Wed, May 13, 2015 at 6:58 PM, Krishantha Samaraweera wrote: > Hi all, > > I have redesign Jacoco coverage generation a bit to support for coverage > merging functionality. Now coverage data dump into > $basedir/target/jacoco/coverage directory at the time

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-13 Thread Krishantha Samaraweera
Hi all, I have redesign Jacoco coverage generation a bit to support for coverage merging functionality. Now coverage data dump into $basedir/target/jacoco/coverage directory at the time of report generation, jacoco coverage data files are merged back to a single file (jacoco-data-merge.exec) and r

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Krishantha Samaraweera
Hi Nuwan, You can't use TestCoverageGenerator anymore (We need to remove this class as well) . The merged report should be generated at the last test module with got executed as we merge all coverage data to common file. May be we can think of introducing pom file to do merging. If this option is

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Nuwan Wimalasekara
Hi Krishantha, I am getting below error when merging the coverage reports. generateReports implementation is missing in CodeCoverageUtils. report module use the org.wso2.carbon.integration.common.utils.coverage.TestCoverageGenerator to aggregate results. Exception in thread "main" java.lang.NoSuch

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Nuwan Wimalasekara
Yes. The correct implementation is org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension. We will remove the CarbonServerExtension from utils to get rid of conflicts. Thanks, Nuwanw On Tue, May 5, 2015 at 9:27 PM, Krishantha Samaraweera wrote: > Hi Nuwan, > > You sh

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Krishantha Samaraweera
Hi Nuwan, You should remove org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension not the org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension. Thanks, Krishantha. On Wed, May 6, 2015 at 9:47 AM, Nuwan Wimalasekara wrote: > Hi > We should

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Nuwan Wimalasekara
Hi We should remove org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension from extensions. Then all the tests module should refer the correct class. Thanks, Nuwanw On Tue, May 5, 2015 at 8:49 PM, Krishantha Samaraweera wrote: > Hi Waruna, > > On Wed, May 6, 2015 at 9

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Krishantha Samaraweera
Hi Waruna, On Wed, May 6, 2015 at 9:12 AM, Waruna Perera wrote: > Hi Krishantha, > > And we need to update Automation.xml to use following class instead of one > from utils. > Please remove the CarbonServerExtension class at utils. Its was deprecated in last release and moved to test extensions

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Waruna Perera
Hi Krishantha, And we need to update Automation.xml to use following class instead of one from utils. org.wso2.carbon.automation.extensions.servers.carbonserver.CarbonServerExtension Thanks On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalasekara wrote: > Hi Krishantha, > I tried generating covera

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Krishantha Samaraweera
Hi Nuwan, What is the exact issue ? Please check whether java.io.tmpdir directory is set to another in test module pom files. Normally coverage data should be appended to jacoco.exec file at tmp dir when running each test module. Thanks, Krishantha. On Tue, May 5, 2015 at 6:29 PM, Nuwan Wimalas

Re: [Dev] Testing Jacoco based code coverage genration

2015-05-05 Thread Nuwan Wimalasekara
Hi Krishantha, I tried generating coverage in ESB. It is working fine and Coverage reports generated. However the coverage report aggregation seems not working when there are multiple tests modules. We need to fix the issue. test-automation-framework - 4.3.2-SNAPSHOT carbon-platform-integration-ut

Re: [Dev] Testing Jacoco based code coverage genration

2015-04-29 Thread Krishantha Samaraweera
Correction : Step #1 configuration should be as follows. copy-jacoco-dependencies compile copy-dependencies ${project.build.directory}/jacoco jar org.jacoco.agent Thanks, Krishantha. On Thu, Apr 30, 2015 at 2:50 AM, Krishantha Samaraw

[Dev] Testing Jacoco based code coverage genration

2015-04-29 Thread Krishantha Samaraweera
Hi all, New coverage implementation using Jacoco has been committed to master branch of carbon-platform-integration. I tried my best to adhere to existing Emma based design and reuse same instrumentation and filters text files. Note that this new coverage implementation was done to support for JDK