Hi Krishantha, There were few performance improvements done for b4p extension. However, this problem may be due to some issue with poms. Will check and get back to you.
regards Nandika On Tue, Jul 1, 2014 at 10:25 AM, Krishantha Samaraweera <[email protected] > wrote: > Hi BPS team, > > I'am checking BPS code coverage generation and found very strange behavior > when include certain packages to code coverage. > > Once I include the package "org.wso2.carbon.bpel.b4p", code coverage > report generates without LOC (line of code) coverage. Excluding this > package for code coverage generation won't work, because there are other > packages with human task causing the same behavior. I see lot of > auto-generated classes with some weird class names included to coverage, > I'm still trying to isolate the problematic packages. > > We don't see the same behavior with other GIT based products. And coverage > generation works fine for BPS 3.2.0. Have done any modifications to code > base recently. Any clue on this behavior will be really appreciated. > > You can find the sample report generated for one test module below. Note > that LOC coverage column is missing. > > OVERALL COVERAGE SUMMARY name block, %method, % class, % all classes > 11% (43347/379631) 15% (2454/16061) 26% (354/1375) > > > Thanks, > Krishantha. > > > -- > Krishantha Samaraweera > Senior Technical Lead - Test Automation > Mobile: +94 77 7759918 > WSO2, Inc.; http://wso2.com/ > lean . enterprise . middlewear. > -- Nandika Jayawardana Senior Technical Lead WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
