Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of sean.xx.qiu@gmail.com
 designates 209.85.132.249 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=apEEP4lXmNYVBhlvgJSWg5nJ9OYNoaITPFA5aPxAmzw4eLhd78FSHFW1zYcb36DxOSfqsk53Ho97PsCXB6zPpJErueQ7mlOmOAHjBOacQZOccOnnrRP+phfKy/rumUuhlPQPRQLQ2u87hDVoXyLDhLbOAi7mun/Rqlb9mLZc3Qs=
Message-ID: <94d710af0709101855y35270de7qd39434fc8dc16905@mail.gmail.com>
Date: Tue, 11 Sep 2007 09:55:26 +0800
From: "Sean Qiu" <sean.xx.qiu@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [build test] Integrate Emma into BTI 2.0 to get code coverage
 report
In-Reply-To: <94d710af0709092338t72358427ua81d7e8d87ed1216@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4831_11001798.1189475726033"
References: <94d710af0709092338t72358427ua81d7e8d87ed1216@mail.gmail.com>

------=_Part_4831_11001798.1189475726033
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Or we can add a new adapor for the emma task, called "emma" as a example.
The benifit is we needn't modify the main script.

1. emma/parameter.xml
    make it depends "classlib" and "drlvm", get the latest built jre for
instrument.
    tell the instrumented jre location as a shared parameter
2. emma/adaptor.xml
    instrument the jre
3. setup wanted test to get coverage report.
    set wanted test suites' depends parameter to "emma", and take the
instrumented jre as the test jre.
4. run the test to get coverage report

But i think there is a little violation against the bti adaptor's
abstraction, so i prefer the previous one.

Any suggestion or commets?

2007/9/10, Sean Qiu <sean.xx.qiu@gmail.com>:
>
> Hi, guys
>
> Shall we integrate the emma into our BTI 2.0 to get the test coverage
> report?
> AFAIK, Robert has spent a number of time on using our unit test to emma
> coverage report.
> Maybe we can generate the coverage from the BTI test besides our unit
> test.
>
> IMHO, we can maintain a individual target as the "run-cc" target in
> script/main.xml, like "run-coverage" or something else.
> It will set up its requisite like an instrumented jre to run the test.
> Before running the test, we need to add <jvmarg
> value="-Xbootclasspath/p:${instrumented-classlib}"> for each adaptor's
> tested jvm task.
>
> Finally, the "run-coverage" command call each adaptor as normal except
> assigning the ${instrumented-classlib} to the instrumented classlib jars.
> The generated report can be placed to build/coverage-report or some more
> proper places.
>
> I think this approach can extend the BTI 2.0 without
> too many modifications.
> Are there any comments about this?  Or any other approach? Any
> suggestion is welcomed.
>
> --
> Sean Qiu
> China Software Development Lab, IBM
>


-- 
Sean Qiu
China Software Development Lab, IBM

------=_Part_4831_11001798.1189475726033--