Thanks Niranjan. We can re-use the same! :-) @Dharshana, per component coverage report is already there. The aggregated report is in addition to that. The aggregated report will depict the overall coverage of the repo to understand how much of this repo's code are covered. Both these are important.
Best regards, KasunG On Tue, Jan 17, 2017 at 11:19 AM, Dharshana Warusavitharana < dharsha...@wso2.com> wrote: > Hi All, > > Considering a component the component should depict a coverage in a single > coverage report. As our current tests in Kernal it seems we have coverage > per repo. But for componats we have to consider coverage in component > separately. > > There for we have to consider coverage per component (Unit +OSGI for > component). > > Thank you, > Dharshana. > > On Tue, Jan 17, 2017 at 9:54 AM, Niranjan Karunanandham <niran...@wso2.com > > wrote: > >> Hi KasunG / Dharshana, >> >> On Mon, Jan 16, 2017 at 9:34 PM, KasunG Gajasinghe <kas...@wso2.com> >> wrote: >> >>> Hi Dharshana, >>> >>> To get a proper understanding of the actual coverage, merging of all the >>> jacoco coverages is a must. It may be to merge the coverage of unit tests >>> and osgi tests together. It could also be extended to generate coverage of >>> tests across repos as well. >>> >> >> As you mentioned in a repo there can be multiple components, each having >> its units tests and OSGi tests. In kernel, we have combined all the tests >> (both unit and OSGi) and create a coverage report [1]. >> >> >>> For example, we have a repo dependency hierarchy like the following. If >>> we could get coverage per-repo as well across all the repos, that'll be >>> beneficial as well. >>> >>> carbon-security <-- carbon-identity-mgt <-- product-is >>> >>> So, we need to have this capability in our products. Can you provide >>> your input here on how we can achieve this? A sample config would be great. >>> >> >>> Thanks, >>> KasunG >>> >>> -- >>> >>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >>> email: kasung AT spamfree wso2.com >>> linked-in: http://lk.linkedin.com/in/gajasinghe >>> blog: http://kasunbg.org >>> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813 >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> [1] - https://github.com/wso2/carbon-kernel/blob/master/tests/ >> coverage-report/pom.xml >> >> Regards, >> Nira >> >> -- >> >> >> *Niranjan Karunanandham* >> Associate Technical Lead - WSO2 Inc. >> WSO2 Inc.: http://www.wso2.com >> >> > > > -- > > Dharshana Warusavitharana > Associate Technical Lead > WSO2 Inc. http://wso2.com > email : dharsha...@wso2.com <dharsha...@wso2.com> > Tel : +94 11 214 5345 > Fax :+94 11 2145300 <011%202%20145300> > cell : +94770342233 <077%20034%202233> > blog : http://dharshanaw.blogspot.com > > lean . enterprise . middleware > -- *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. email: kasung AT spamfree wso2.com linked-in: http://lk.linkedin.com/in/gajasinghe blog: http://kasunbg.org phone: +1 650-745-4499, 77 678 0813
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
