Skip to main content

Integrating code coverage tool JaCoCo in your play 2.1.x project

I've been looking into code coverage for Play 2.1.x and found that the only
good option is Jacoco.

Its always good to have a fine test coverage in any project. I am working on Play framework & this time i’ve tried to integrate the JaCoCo with my play java project & it’s cool to have it in my project.

There are few easy steps to integrate the JaCoCo in Play project.

1. Add the following lines of code in your plugin.sbt file. You’ve to add the plugin dependency to your project’s plugins.sbt.

libraryDependencies ++= Seq(
  "org.jacoco" % "org.jacoco.core" % "0.5.9.201207300726" artifacts(Artifact("org.jacoco.core", "jar", "jar")),
  "org.jacoco" % "org.jacoco.report" % "0.5.9.201207300726" artifacts(Artifact("org.jacoco.report", "jar", "jar")))




addSbtPlugin("de.johoop" % "jacoco4sbt" % "1.2.4")















2. Have this import in your Build.scala file.















import de.johoop.jacoco4sbt.JacocoPlugin._









3. Add the following line in your Build.scala file.















lazy val jacoco_settings = Defaults.defaultSettings ++ Seq(jacoco.settings: _*)









4. Add these settings in to your Play project in Build.scala file as















val main = PlayProject(appName, appVersion, appDependencies, settings = jacoco_settings).settings( 



parallelExecution in jacoco.Config := false,



jacoco.excludes in jacoco.Config := Seq("views.*", "controllers.Reverse*", "controllers.javascript.*", "controllers.ref.*", "Routes*") 







)













5. That’s it. Lets run the JaCoCo with command jacoco:cover 











Jacoco integration 









6. You’ll find the html file with name index.html which would give 
you the full test report. You’ll find this file  in this path /target/scala-2.10/jacoco/html



This is how your coverage report would look like :





Jacoco integration





Jacoco integration





















Labels:






























Comments











Post a Comment































Popular posts from this blog





















JavaMelody: Monitoring the Performance of Tomcat Application Server




























 Javamelody  is an opensource (LGPL) application to monitor Java or Java EE application servers in QA and production environments.  JavaMelody is mainly based on statistics of requests and on evolution charts.  (Extract from the Javamelody home page)   It allows to improve applications in QA and production  Give facts about the average response times and number of executions  Make decisions when trends are bad, before problems become too serious  Optimize based on the more limiting response times  Find the root causes of response times  Verify the real improvement after optimization   It includes summary charts showing the evolution over time of the following indicators:   Number of executions, mean execution times and percentage of errors  of http requests, sql requests, jsp pages or methods of business  façades (if EJB3, Spring or Guice)  Java memory  Java CPU  Number of user sessions  Number of jdbc connections   These charts can be viewed on the current day, week, month, year or cu...




















Post a Comment









Read more




























Tomcat Clustering : Session Replication with Backup Manager




























 Prerequisite Blogs:    How To Install Apache Tomcat   Multiple Tomcat Instances on Single Machine   Tomcat Clustering: Loadbalancing with mod_jk and Apache   Tomcat Clustering : Session Affinity         Backup Manager   Backup manager usually used clustered environment. Its like delta manger. But it will  replicate to exactly one other instance(backup instance).  Its act  like one instance is Primary  and another instance as backup.      Steps to make Session Replication in Tomcat Clustering    I am continue from exactly where I left in last session affinity post . So check that post and make sure jumRoute all are set properly. Steps are     Enable Multicast routing  Add <Cluster> Entries in conf/server.xml file for all instances.  Enable the Web Application as distributable     Step1:  Enable Multicast routing     In Linux Environment most of the system kernel is capable to  process the multicast address. We need to add...




















Post a Comment









Read more




























Java HotSpot VM Settings




























       The following JVM parameters are recommended:    -Djava.awt.headless=true   -Dfile.encoding=UTF-8   -server   -Xms512m   -Xmx1024m   -XX:NewSize=256m   -XX:MaxNewSize=256m   -XX:PermSize=256m   -XX:MaxPermSize=256m   -XX:+DisableExplicitGC     -Djava.awt.headless=true   Headless  mode is a system configuration in which the display device, keyboard,  or mouse is lacking. Sounds unexpected, but actually you can perform  different operations in this mode, even with graphic data.    -server   The  JDK includes two flavors of the VM -- a client-side offering, and a VM  tuned for server applications. These two solutions share the Java  HotSpot runtime environment code base, but use different compilers that  are suited to the distinctly unique performance characteristics of  clients and servers. These differences include the compilation inlining  policy and heap defaults. Although the Server and the Client VMs are  similar, the Serv...




















Post a Comment









Read more