Hi Amalka, In this case there are some jars you need to avoid from instrumenting as example all equinox jars. To take coverage in certain product you need only to instrument jars which are related to particular product.
In Instrumentation EMMA what happens is it updates a metatag in jar so it changes MD5 sum and some times default permisions of jars. Use following filters in filter.txt to eliminate unwated jars form instrumenting -*.stub*-*.stub_-*.stub_4.0.0-*.stub--org.eclipse.*-*.equinox.* -org.wso2.carbon.user.core.*-samples.*-*.log4j*-*.axis2*-*.ui*-*.tenant* -*.stratos*-*.eventing*-*transports*-org.wso2.carbon.mediation.statistics* -*startup* Thank You, Dharshana. On Wed, Jan 14, 2015 at 12:17 PM, Amalka Subasinghe <[email protected]> wrote: > Hi all, > > Currently I'm trying to $subject. Since AF integration tests runs in > platform mode, we can't generate code coverage report via our existing test > framework. > > I found a blog we can use for this. [1] > as specified in the blog when I execute the xargs -n 1 > $JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite -cp < > jarlist.txt. > It changes file permissions on appfactory jars, because of that I can't up > the appfactory setup to run the tests. > > Does anyone have ideas on how to do this? > > [1] > http://charithaka.blogspot.com/2009/05/run-time-code-coverage-using-emma.html > > Thanks > Amalka > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dharshana Warusavitharana Senior Software Engineer , Test Automation WSO2 Inc. http://wso2.com email : [email protected] <[email protected]> Tel : +94 11 214 5345 Fax :+94 11 2145300 cell : +94770342233 blog : http://dharshanaw.blogspot.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
