On Fri, Jan 16, 2015 at 1:48 PM, Amalka Subasinghe wrote:
> *Steps to generate the code coverage report for AF*
> [NOTE: did all the steps using afpuppet user]
>
> 1. Create a folder [eg: emma]
>
> 2. Copy the following files to the emma folder
> - emma.jar
> - jarlist file (create a file which c
On Fri, Jan 16, 2015 at 2:24 PM, Amalka Subasinghe wrote:
> Here i'm giving required list of jars using jarlist file (I have attached
> the file).. In that case, do I still need to specify the filter.txt?
>
You still need to filter jars which you have already instrumented and could
cause AF star
Here i'm giving required list of jars using jarlist file (I have attached
the file).. In that case, do I still need to specify the filter.txt?
On Fri, Jan 16, 2015 at 2:18 PM, Dharshana Warusavitharana <
dharsha...@wso2.com> wrote:
> Hi Amalka,
>
> In this case there are some jars you need to avo
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
cha
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 e
