Emma report merging achieved by renaming coverage.ec file after graceful server restart, and providing all *.ec files when creating reports.
Emma doesn't provide a way to generate unique .ec file when jvm exists. Actually it uses same name and overwrite the file at specified location. AFAIU there's no way to change default behavior. Thanks, Krishantha. On Thu, Aug 2, 2012 at 3:29 PM, Afkham Azeez <[email protected]> wrote: > It is better to generate .ec files with unique names, and finally when > creating the reports, provide all those .ec files, and the report will > contain the merged results. > > On Thu, Aug 2, 2012 at 1:21 PM, Krishantha Samaraweera < > [email protected]> wrote: > >> Hi all, >> >> I'm debugging the $subject. It seems that emma mess up code coverage >> after restarting the servers gracefully. Also tried by setting >> emma.coverage.merge=true option in emma.properties, but nothing seems to >> work. >> >> I will try to dump all coverage data to new coverage.ec file before and >> after server restart. Then emma coverage files can be merged when >> generating emma reports. >> >> At the moment this is a blocker for measuring automation hackathon >> outcome. >> >> Thanks, >> Krishantha. >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
