Today we tried to instrument G-reg with Emma but server was not started up. Then we removed some unnecessary jars (jars which are not directly associated with G-reg testing) and was able to run the server.
With this, we should be able to get the run-time test coverage of products. We can easily get the coverage of individual modules when writing tests. Test automation team is going to run Emma against individual G-reg modules and find out the existing test coverage. Regards Charitha On Mon, Feb 28, 2011 at 6:20 PM, Thilini Ishaka <[email protected]> wrote: > > *Steps:* > > 1. Create a jarlist.txt > eg:* find > /home/thilini/Desktop/wso2greg-3.6.0/repository/components/plugins/ >> > /home/thilini/Desktop/wso2greg-3.6.0/repository/components/plugins/jarlist.txt > * (jarlist.txt should contain absolute paths of jars. Remove unwanted > jars from the list. If not there will be issues when starting the server) > > 2. xargs -n 1 $JAVA_HOME/jre/bin/java -cp emma.jar emma instr -m overwrite > -cp < jarlist.txt > 3. ruby dynamicImportsPatcher.rb < jarlist.txt (Before running this step > need to install rubyzip. Use sudo apt-get install libzip-ruby1.8) > 4. Copy emma.jar to */repository/components/plugins, > /repository/components/lib *and */lib *directories. > 4. Start G-Reg > 5. Do the test > 6. Shutdown server > 7. cp wso2greg-3.6.0/coverage.ec . > 8. java -cp emma.jar emma report -r html -in coverage.em,coverage.ec > > Attached *dynamicImportsPatcher.rb *and *emma.jar* files herewith. > > Thanks > > > -- > Thilini Ishaka > email: [email protected] > mobile: +94 718408171 > > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
