![\"emma-overview\"](\"http:\/\/www.scmgalaxy.com\/tutorials\/wp-content\/uploads\/2013\/05\/emma-overview.png\")
Overview<\/h1>\nOverview<\/h1>\nEMMA is a tool for measuring coverage<\/em> of Java software. Such a tool is essential for detecting dead code and verifying which parts of your application are actually exercised by your test suite and interactive use. Advantages of Emma over other coverage tools<\/strong><\/p>\n EMMA differs from other coverage tools in its extreme orientation towards fast<\/em> iterative develop-test style of writing software. JVM Profiler Interface (JVMPI)-based tools do not require an instrumented source build, but the runtime overhead of running with JVMPI on is empirically known to be very high and results in depressingly slow testsuite runs. For tools based on source code instrumentation, having to wait for a full source code rebuild just to check coverage metrics is not something a normal developer wants to do several times during a day. EMMA’s goal is to be so unintrusive<\/em> that frequent daily checking of coverage numbers becomes second nature to every<\/em> developer on the team, if not a completely automatic byproduct of every test run.<\/p>\n Install and Configuration<\/strong><\/p>\n Method 1: To run on Command Line. Implementing EMMA with Application<\/strong><\/p>\n Implement EMMA in J2EE project {WebLogic, Websphere, Tomcat, JBoss, …}?<\/strong><\/p>\n There are very less opportunities given by Emma that\u00a0 you would be able setup emma for J2EE Project on the fly mode. The reason behind this to fact that many J2EE features requires specialized class loading that will happen outside EMMA instrumenting class holder. The server might run fine but you will unlikely to get EMMA report. Notes:<\/strong><\/p>\n Reference: Emma Integration with other tools<\/p>\n Emma Integration with Sonar jar instrumentation using Emma<\/strong><\/p>\n http:\/\/primates.ximian.com\/~flucifredi\/emma-HOWTO.html<\/a> Overview EMMA is a tool for measuring coverage of Java software. Such a tool is essential for detecting dead code and verifying which parts of your application are actually exercised by your test suite and interactive use. EMMA’s design strives for several, very elusive in their combination, goals: report rich coverage analysis data without introducing…<\/p>\n","protected":false},"author":1,"featured_media":3763,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[62],"tags":[2337,1003,784,610,2334,1040,2331,514,2335,2336,341],"class_list":["post-338","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-code-analysis","tag-advantages-of-emma","tag-code","tag-code-analysis","tag-code-coverage","tag-code-coverage-tool","tag-coverage","tag-coverage-tools","tag-emma","tag-emma-overview","tag-overview-of-emma","tag-tool"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=338"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/338\/revisions"}],"predecessor-version":[{"id":3764,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/338\/revisions\/3764"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/3763"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nEMMA’s design strives for several, very elusive in their combination, goals:<\/p>\n\n
\nCopying emma.jar to <your\u00a0jre\u00a0dir>\/lib\/ext\/ directory for whichever JRE you use from command line.
\nMethod 2:
\nStill, if you are wary of adding a third-party library as a standard JRE extension, just make sure that all your EMMA command line invocations add emma.jar to the JVM classpath:
\n>java -cp …\/lib\/emma.jar <emma or emmarun command><\/p>\n\n
\nSo, based Procedures to Instrument your classes prior to deployment (offline mode); offline instrumentation always follows the same compile \/ instrument \/ Package \/ deploy \/ get coverage \/ Generate report sequence.
\nThere are following steps need to follow to implement EMMA in J2EE based project\u2026<\/p>\n\n
\nhttp:\/\/emma.sourceforge.net\/faq.html#q.runtime.appservers<\/a>
\nhttp:\/\/emma.sourceforge.net\/reference\/ch02s03.html#tool-ref.instr.outmodes<\/a><\/p>\n
\nEmma Integration with Hudson
\nEmma Integration with CruiseControl<\/p>\n
\nhttp:\/\/emma.sourceforge.net\/reference\/ch02s03.html#tool-ref.instr.outmodes<\/a>
\nhttp:\/\/primates.ximian.com\/~flucifredi\/emma-HOWTO.html<\/a>
\nhttp:\/\/groovy.329449.n5.nabble.com\/EMMA-Code-Coverage-has-problem-with-Groovy-classes-td360560.html<\/a><\/p>\n<\/h1>\n","protected":false},"excerpt":{"rendered":"