Return-Path: Delivered-To: apmail-harmony-dev-archive@www.apache.org Received: (qmail 93143 invoked from network); 11 Sep 2007 09:25:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Sep 2007 09:25:35 -0000 Received: (qmail 36900 invoked by uid 500); 11 Sep 2007 09:25:27 -0000 Delivered-To: apmail-harmony-dev-archive@harmony.apache.org Received: (qmail 36863 invoked by uid 500); 11 Sep 2007 09:25:27 -0000 Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list dev@harmony.apache.org Received: (qmail 36854 invoked by uid 99); 11 Sep 2007 09:25:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2007 02:25:27 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of liyilei1979@gmail.com designates 209.85.134.189 as permitted sender) Received: from [209.85.134.189] (HELO mu-out-0910.google.com) (209.85.134.189) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Sep 2007 09:25:25 +0000 Received: by mu-out-0910.google.com with SMTP id w1so1925079mue for ; Tue, 11 Sep 2007 02:25:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=DVmf9fP9Djb2a4ZSoJxH5qY9tvbAZMjUEzuqmuROQro=; b=J4DZj5VJ1BEvrXkuNjY6u21Bykt/uZwd2lQI//8qel9jDubM6eDZtTDrpdJJ53RhxLTQdVElvmwygp1JEGYw6vPzLaWg/Sh1mHB0LbAz9iFBUDgaFgK/WoCz8VHIGZu+0PVOXYURr/yLv1OOE0yGP+PQBoKiFqXIsx+mZcnhPoI= 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:content-transfer-encoding:content-disposition:references; b=im88vw1fwpnkFrN/mYo33n0e1KdQ3a5Yjj6FsgrHNXdRlnYFTAAjfL/SyQyPgoWHMij8qXub9PxSDxAok+KtOa/mGm5sx41FqR2kCA/HnKcssujqEXWJ3UQl81zxw9l8Y9XKGBW5qdxy2B6nt50mOY3VrHbcBuqi3mp0nbPBvjA= Received: by 10.82.181.10 with SMTP id d10mr3473371buf.1189502702895; Tue, 11 Sep 2007 02:25:02 -0700 (PDT) Received: by 10.82.159.3 with HTTP; Tue, 11 Sep 2007 02:25:02 -0700 (PDT) Message-ID: Date: Tue, 11 Sep 2007 17:25:02 +0800 From: "Leo Li" To: dev@harmony.apache.org Subject: Re: [build test] Integrate Emma into BTI 2.0 to get code coverage report In-Reply-To: <94d710af0709101855y35270de7qd39434fc8dc16905@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <94d710af0709092338t72358427ua81d7e8d87ed1216@mail.gmail.com> <94d710af0709101855y35270de7qd39434fc8dc16905@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org On 9/11/07, Sean Qiu wrote: > 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? Besides, I have put a kernel classes list on harmony wiki.[1] You may try it, Sean.:) It is generated by a simulation of emma's gathering coverage data. If any future modification in harmony's code influences the emma depending classes, a solution to generate kernel classes list is also included in the wiki page[2]. Good luck! [1]http://wiki.apache.org/harmony-data/attachments/coverageEMMA/attachments/kernel.classes.list [2]http://wiki.apache.org/harmony/coverageEMMA > > 2007/9/10, Sean Qiu : > > > > 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 > 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 > -- Leo Li China Software Development Lab, IBM