+1. At the moment, we need to find the coverage provided by existing tests. So it does not matter whether the server is running locally or not.
/Charitha On Tue, May 29, 2012 at 11:50 AM, Krishantha Samaraweera < krishan...@wso2.com> wrote: > Hi Dharshana, > > Shall we focus on Emma to get coverage. Lets assume all the builds are > running locally. In next phase we can work on JaCoCo on-the-fly > instrumentation or evaluate another tool. > > Thanks, > Krishantha. > > On Thu, Apr 19, 2012 at 12:39 AM, Dharshana Warusavitharana < > dharsha...@wso2.com> wrote: > >> Hi All, >> For code coverage we are working on On-the- fly instrumentation using >> a java agent hook. JaCoCo seems to be a good option. By this we can >> instrument the jar while loading to JVM with out modifying the target >> jar. >> >> For distributed environment we are planned to plant a agent in server >> side and retrieve results to Clarity by a application hosted in a >> server side. The instrumenting Java agent hook is in progress. >> >> I'm working on the architecture and and will update the progress. >> >> Thank You, >> Dharshana. >> >> On Tue, Apr 17, 2012 at 12:14 PM, Krishantha Samaraweera >> <krishan...@wso2.com> wrote: >> > I think we can't use the Emma based framework, it uses carbon home to >> > instrument jars. System test framework doesn't depends on carbon home >> as it >> > assumes all servers are running remotely. One possible option would be >> to >> > run the serves locally and use Emma based framework to get code >> coverage. >> > >> > Thanks, >> > Krishantha. >> > >> > On Tue, Apr 17, 2012 at 11:07 AM, Afkham Azeez <az...@wso2.com> wrote: >> >> >> >> Can't you use the new Emma based framework I wrote recently & which is >> >> used with standard product integration tests? >> >> >> >> On Tue, Apr 17, 2012 at 10:58 AM, Krishantha Samaraweera >> >> <krishan...@wso2.com> wrote: >> >>> >> >>> We are trying to integrating code coverage tool with System test >> >>> framework (Clarity). Since the framework was designed to run with >> >>> distributed product platform, we got to sort out remote jar >> >>> instrumentation when using emma. The plan is to have platform wide >> coverage >> >>> and individual product coverage. There are few >> alternative approaches to >> >>> over come the difficulty, Dharshana please update your findings. >> >>> >> >>> Thanks, >> >>> Krishantha. >> >>> >> >>> _______________________________________________ >> >>> Dev mailing list >> >>> Dev@wso2.org >> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >>> >> >> >> >> >> >> >> >> -- >> >> Afkham Azeez >> >> Director of Architecture; WSO2, Inc.; http://wso2.com >> >> Member; Apache Software Foundation; http://www.apache.org/ >> >> >> >> email: az...@wso2.com cell: +94 77 3320919 >> >> blog: http://blog.afkham.org >> >> twitter: http://twitter.com/afkham_azeez >> >> linked-in: http://lk.linkedin.com/in/afkhamazeez >> >> >> >> Lean . Enterprise . Middleware >> >> >> > >> > >> > _______________________________________________ >> > Dev mailing list >> > Dev@wso2.org >> > http://wso2.org/cgi-bin/mailman/listinfo/dev >> > >> >> >> >> -- >> >> Dharshana Warusavitharana >> Software Engineer , Test Automation >> WSO2 Inc. http://wso2.com >> email : dharsha...@wso2.com >> cell : +94772202595 >> blog : http://dharshanaw.wordpress.com/ >> >> lean . enterprise . middleware >> > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
