<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>JavaToolbox Category : Code coverage</title>
    <link>https://javatoolbox.com/categories/code-coverage</link>
    <description>Category of tools referenced on JavaToolbox.com</description>
    <managingEditor>info@NOJavaToolboxSPAM.com</managingEditor>
    <webMaster>info@NOJavaToolboxSPAM.com</webMaster>
    <language>en</language>
    <copyright>Fabrice Marguerie</copyright>
    <pubDate>Fri, 17 Apr 2026 07:44:45 GMT</pubDate>
    <lastBuildDate>Fri, 17 Apr 2026 07:44:45 GMT</lastBuildDate>
    <ttl>60</ttl>
    <image>
      <url>https://z.javatoolbox.com/style/LogoForRss.png</url>
      <title>JavaToolbox Category : Code coverage</title>
      <link>https://javatoolbox.com/categories/code-coverage</link>
    </image>
    <item>
      <title>UnitCover</title>
      <link>https://javatoolbox.com/tools/unitcover</link>
      <guid>https://javatoolbox.com/tools/unitcover</guid>
      <pubDate>Fri, 01 Sep 2006 11:11:51 GMT</pubDate>
      <description>&lt;p&gt;Code coverage viewer plugin for NetBeans 5.
&lt;br /&gt;&lt;br /&gt;UnitCover displays the code coverage of unit tests in the NetBeans editor. As unit tests are run, the module will update the code coverage data and markup the editors lines accordingly. The lines which are fully covered by unit tests are annotated with a green color and the ones covered partially are annotated in yellow.
&lt;br /&gt;The functionality provided by the plugin helps to visually identify the portions of code with low coverage and helps in targeted tests development.
&lt;br /&gt;Java Application, Java Library, Java Project with Existing Sources and NetBeans module projects are supported.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/unitcover"&gt;more about UnitCover&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Optimizeit Enterprise Suite</title>
      <link>https://javatoolbox.com/tools/optimizeit-enterprise-suite</link>
      <guid>https://javatoolbox.com/tools/optimizeit-enterprise-suite</guid>
      <pubDate>Sun, 02 Jan 2005 04:28:47 GMT</pubDate>
      <description>&lt;p&gt;Equips developers with a toolkit for optimizing performance and managing application quality throughout development.
&lt;br /&gt;Optimizeit Enterprise Suite allows developers to track performance bottlenecks at the JDBC, JMS, JNDI, JSP, and EJB level. It integrates with popular application servers and IDEs, and it supports multiple operating systems. 
&lt;br /&gt;Optimizeit Enterprise Suite includes:
&lt;br /&gt;- Optimizeit Profiler: isolate memory and CPU performance issues.
&lt;br /&gt;- Optimizeit Thread Debugger: solve thread issues. View the status of all threads and monitors in real time, avoid thread starvation and contentions that lead to crashes, and predict deadlocks before they occur.
&lt;br /&gt;- Optimizeit Code Coverage: view in real time how frequently each class, method, and line of code is executed. Code Coverage can be included in automated batch testing sessions, and it allows for report generation.
&lt;br /&gt;- Optimizeit Request Analyzer: analyze the performance behavior of code across J2EE application tiers.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/optimizeit-enterprise-suite"&gt;more about Optimizeit Enterprise Suite&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>IntelliJ IDEA</title>
      <link>https://javatoolbox.com/tools/intellij-idea</link>
      <guid>https://javatoolbox.com/tools/intellij-idea</guid>
      <pubDate>Tue, 21 Dec 2004 00:49:00 GMT</pubDate>
      <description>&lt;p&gt;Java IDE focused on developer productivity.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Multiple projects support
&lt;br /&gt;- Refactoring
&lt;br /&gt;- Java EE (J2EE), Java SE (J2SE), Java ME (J2ME) support
&lt;br /&gt;- Supported languages: Java, JavaScript/ Flex, HTML/XHTML/CSS, XML/XSL, Ruby/JRuby, Groovy
&lt;br /&gt;- Technologies and frameworks supported: JSP, JSF, EJB, AJAX, GWT, Struts, Spring, Seam, Hibernate/ JPA, Web Services, Rails, Grails, Java ME MIDP/CLDC, OSGi, Google App Engine, Tapestry, Android
&lt;br /&gt;- Support for SQL-92 and MySQL
&lt;br /&gt;- Support for FreeMarker and Velocity
&lt;br /&gt;- Integration with Ant, JUnit, TestNG and Maven
&lt;br /&gt;- Integration with CVS, Subversion, StarTeam, Perforce, ClearCase UCM and Visual SourceSafe version control systems
&lt;br /&gt;- Supports ER diagrams with EJB3
&lt;br /&gt;- Swing GUI designer
&lt;br /&gt;- IDE customization
&lt;br /&gt;- Code generation
&lt;br /&gt;- Code analysis
&lt;br /&gt;- PHP support
&lt;br /&gt;- Free and open-source IDE for Java SE, Groovy and Android&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/intellij-idea"&gt;more about IntelliJ IDEA&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cobertura</title>
      <link>https://javatoolbox.com/tools/cobertura</link>
      <guid>https://javatoolbox.com/tools/cobertura</guid>
      <pubDate>Mon, 21 Mar 2005 15:02:50 GMT</pubDate>
      <description>&lt;p&gt;Free Java tool that calculates the percentage of code accessed by tests.
&lt;br /&gt;Cobertura can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Can be executed from Ant or from the command line.
&lt;br /&gt;- Instruments Java bytecode after it has been compiled.
&lt;br /&gt;- Can generate reports in HTML or XML.
&lt;br /&gt;- Shows percent of lines coveraged and branches coveraged for each class, package, and for the overall project.
&lt;br /&gt;- Shows the McCabe cyclomatic code complexity of each class, and the average cyclomatic code complexity for each package, and for the overall product.
&lt;br /&gt;- Can sort HTML results by class name, percent of lines covered, percent of branches covered, etc. It can also sort in ascending or descending order.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/cobertura"&gt;more about Cobertura&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>EMMA</title>
      <link>https://javatoolbox.com/tools/emma</link>
      <guid>https://javatoolbox.com/tools/emma</guid>
      <pubDate>Mon, 24 Jan 2005 18:03:57 GMT</pubDate>
      <description>&lt;p&gt;Open-source toolkit for measuring and reporting Java code coverage.
&lt;br /&gt;EMMA is based on bytecode instrumentation. 
&lt;br /&gt;Features include:
&lt;br /&gt;- Can instrument classes for coverage either offline (before they are loaded) or on the fly (using an instrumenting application classloader).
&lt;br /&gt;- Supported coverage types: class, method, line, basic block. EMMA can detect when a single source code line is covered only partially.
&lt;br /&gt;- Coverage stats are aggregated at method, class, package, and "all classes" levels.
&lt;br /&gt;- Output report types: plain text, HTML, XML. All report types support drill-down, to a user-controlled detail depth. The HTML report supports source code linking.
&lt;br /&gt;- Output reports can highlight items with coverage levels below user-provided thresholds.
&lt;br /&gt;- Coverage data obtained in different instrumentation or test runs can be merged together.
&lt;br /&gt;- Does not require access to the source code and degrades gracefully with decreasing amount of debug information available in the input classes.
&lt;br /&gt;- Can instrument individual .class files or entire .jars (in place, if desired). Coverage subset filtering is possible, too.
&lt;br /&gt;- Makefile and ANT build integration are supported on equal footing.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/emma"&gt;more about EMMA&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hansel</title>
      <link>https://javatoolbox.com/tools/hansel</link>
      <guid>https://javatoolbox.com/tools/hansel</guid>
      <pubDate>Mon, 19 Sep 2005 19:12:06 GMT</pubDate>
      <description>&lt;p&gt;Hansel is an extension to JUnit that adds code coverage testing to the testing framework. &lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/hansel"&gt;more about Hansel&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clover</title>
      <link>https://javatoolbox.com/tools/clover</link>
      <guid>https://javatoolbox.com/tools/clover</guid>
      <pubDate>Tue, 21 Dec 2004 00:21:24 GMT</pubDate>
      <description>&lt;p&gt;Configurable code coverage analysis tool.
&lt;br /&gt;Clover highlights sections of code that are not being adequately exercised by your unit tests.
&lt;br /&gt;Main features:
&lt;br /&gt;- plug-ins for IntelliJ IDEA, Eclipse, NetBeans, JBuilder and JDeveloper.NET 2003
&lt;br /&gt;- integration with projects using Ant
&lt;br /&gt;- integration into legacy build systems with command line interface and API
&lt;br /&gt;- configurable coverage reporting of Method, Statement, and Branch coverage
&lt;br /&gt;- reporting in HTML, XML, PDF, and plain text
&lt;br /&gt;- standalone Swing Viewer providing interactive browsing of source-level coverage results
&lt;br /&gt;- control over the instrumentation and coverage recording process, using source level directives, regexp-based filters and runtime system properties&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/clover"&gt;more about Clover&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JProbe Suite</title>
      <link>https://javatoolbox.com/tools/jprobe-suite</link>
      <guid>https://javatoolbox.com/tools/jprobe-suite</guid>
      <pubDate>Tue, 06 Jun 2006 09:51:47 GMT</pubDate>
      <description>&lt;p&gt;Java profiler providing diagnostics on memory usage, performance and test coverage.
&lt;br /&gt;&lt;br /&gt;JProbe Suite includes:
&lt;br /&gt;- JProbe Memory: for proactively discovering, diagnosing and resolving memory allocation issues such as memory leaks (loitering objects) and excessive garbage collection activity (object cycling) that can lead to out-of-memory system crashes and slower overall system performance.
&lt;br /&gt;- JProbe Performance: for proactively discovering, diagnosing and resolving code bottlenecks such as expensive methods, deadlocks and stalled threads that can lead to slow application performance and limit scalability.
&lt;br /&gt;- JProbe Coverage: for proactively assessing the completeness and accuracy of test runs in development and QA – enhances development and QA collaboration in creating more complete test suites.
&lt;br /&gt;&lt;br /&gt;JProbe also offers an Eclipse plug-in that provides code performance analysis and problem resolution directly within the Eclipse Java IDE.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jprobe-suite"&gt;more about JProbe Suite&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>McCabe IQ</title>
      <link>https://javatoolbox.com/tools/mccabe-iq</link>
      <guid>https://javatoolbox.com/tools/mccabe-iq</guid>
      <pubDate>Mon, 15 Sep 2008 13:24:07 GMT</pubDate>
      <description>&lt;p&gt;Interactive, visual environment for managing software quality through static analysis and test/code coverage.
&lt;br /&gt;McCabeIQ comes in three editions: Developers, Test Team, Enterprise.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Software metrics: McCabe Cyclomatic Complexity; McCabe Essential Complexity; Module Design Complexity; Integration Complexity; Lines of Code; Halstead.
&lt;br /&gt;- Color-coded structure Battlemaps, scatter plot diagrams, and flow graphs
&lt;br /&gt;- Metric Trend Reports: track a system's metric values over time to document the progress made in improving the overall stability and quality of the project
&lt;br /&gt;- Customized reporting
&lt;br /&gt;- Plan software testing resources in advance, identifying test paths and the number of tests required
&lt;br /&gt;- Code coverage
&lt;br /&gt;- McCabe Compare: helps you locate redundant code so you can either delete or reengineer it
&lt;br /&gt;- McCabe Data: track data use within your programs and anticipate complexity
&lt;br /&gt;- McCabe Change: identify the modules in your program that have changed since the first time you parsed your code
&lt;br /&gt;- McCabe Slice: uncover your program’s internal architecture
&lt;br /&gt;- Supports Ada, ASM86/95, C, C#, C++.NET, C++, Cobol, Fortran, Java, JSP, Perl, PL1, VB, VB.NET
&lt;br /&gt;- Enterprise Edition provides all the functionality of the Developers and Test Team Editions. In addition, it provides enterprise reporting, reengineering capabilities, change analysis, and secure web-enabled test data collection.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/mccabe-iq"&gt;more about McCabe IQ&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>jcoverage</title>
      <link>https://javatoolbox.com/tools/jcoverage</link>
      <guid>https://javatoolbox.com/tools/jcoverage</guid>
      <pubDate>Mon, 21 Mar 2005 14:58:36 GMT</pubDate>
      <description>&lt;p&gt;jcoverage identifies how many times each line of code in your application has been executed and you can see which parts of your software remain untested. After instrumenting your code and running your tests, a report is generated allowing you to view information coverage figures from a project level right down to the individual line of code.
&lt;br /&gt;jcoverage works by modifying your Java classes at the bytecode level. It also works against code that you do not have the source code for, as well as code that has itself been modified at byte-code level, for example, JDO data classes and aspect-derived code. When these modified classes are executed, during a test-run for instance, data is collected that identifies how many times each line of code has been executed. 
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- measure the percentage of code that has been tested.
&lt;br /&gt;- run your tests, create your reports, get all information about problems in your system (with data shown on a per-test basis).
&lt;br /&gt;- set-up your test in isolation using mock-object technologies to reduce reliance on extensive end-to-end per system tests.
&lt;br /&gt;&lt;br /&gt;Three versions are available: jcoverage/gpl (free version released under the GPL); jcoverage commercial edition (fully supported); jcoverage+ (introduces more rigour and finer granularity to your testing).
&lt;br /&gt;A commercial jcoverage plugin is available for Eclipse 3.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jcoverage"&gt;more about jcoverage&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>EclEmma</title>
      <link>https://javatoolbox.com/tools/eclemma</link>
      <guid>https://javatoolbox.com/tools/eclemma</guid>
      <pubDate>Sat, 21 Oct 2006 12:03:48 GMT</pubDate>
      <description>&lt;p&gt;Code coverage tool for Eclipse.
&lt;br /&gt;Internally, EclEmma is based on the EMMA Java code coverage tool, trying to adopt EMMA's philosophy for the Eclipse workbench:
&lt;br /&gt;- Fast develop/test cycle: Launches from within the workbench like JUnit test runs can directly be analyzed for code coverage.
&lt;br /&gt;- Coverage results are immediately summarized and highlighted in the Java source code editors.
&lt;br /&gt;- Non-invasive: does not require modifying your projects or performing any other setup.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Launching: EclEmma adds a so called launch mode to the Eclipse workbench. It is called Coverage mode and works exactly like the existing Run and Debug modes.
&lt;br /&gt;- Analysis: After your application or unit test has terminated code coverage information is automatically available in the Eclipse workbench (Coverage overview, Source highlighting). Additional features support analysis for your test coverage (Different counters, Multiple coverage sessions, Merge Sessions)
&lt;br /&gt;- Import/Export: Coverage data import, Coverage report export as a .ec file or in XML or HTML format&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/eclemma"&gt;more about EclEmma&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>TeamCity</title>
      <link>https://javatoolbox.com/tools/teamcity</link>
      <guid>https://javatoolbox.com/tools/teamcity</guid>
      <pubDate>Fri, 21 Jul 2006 01:20:52 GMT</pubDate>
      <description>&lt;p&gt;IDE-independent integrated team environment.
&lt;br /&gt;TeamCity automates and coordinates key collaborative processes to eliminate manual systems and delays, providing integration with multiple build and test tools, real-time unit test frequency, server-side inspections and code coverage analysis.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- continuous integration and testing
&lt;br /&gt;- server-side code analysis
&lt;br /&gt;- build management
&lt;br /&gt;- automated team communication
&lt;br /&gt;- code coverage analysis and reporting
&lt;br /&gt;- web-based interface and project dashboard
&lt;br /&gt;- extensibility
&lt;br /&gt;- IntelliJ IDEA, Eclipse and Visual Studio integration
&lt;br /&gt;- pre-tested (delayed) commit
&lt;br /&gt;- remote run for personal builds
&lt;br /&gt;&lt;br /&gt;Supported environments:
&lt;br /&gt;- Ant, Maven, NAnt, MSBuild
&lt;br /&gt;- Having an IntelliJ IDEA project or a Visual Studio solution, you can build your application with TeamCity, even without providing a build script
&lt;br /&gt;- Supports JUnit and NUnit
&lt;br /&gt;- Integrates with Perforce, CVS, Subversion, Visual SourceSafe, StarTeam&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/teamcity"&gt;more about TeamCity&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Codign CoView</title>
      <link>https://javatoolbox.com/tools/codign-coview</link>
      <guid>https://javatoolbox.com/tools/codign-coview</guid>
      <pubDate>Thu, 22 Jun 2006 01:03:53 GMT</pubDate>
      <description>&lt;p&gt;Eclipse plug-ins and Ant task that provide unit tests and coverage data for Java applications.
&lt;br /&gt;CoView consists of:
&lt;br /&gt;- CoViewDeveloper: helps developers improve the testability of their code, design and generate JUnit tests, highlight paths and measure path coverage.
&lt;br /&gt;- CoViewManager: helps managers define quality standards and check coverage before code is released into production.
&lt;br /&gt;- Comet: available for Ant, lets you measure your metrics during the build process.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- CoView JUnit Runner for running tests
&lt;br /&gt;- In addition to JUnit support, CoViewDeveloper also has wizards for HTTPUnit and DbUnit, as well as support for abstract classes and private methods
&lt;br /&gt;- Immediate metric analysis
&lt;br /&gt;- User-defined testability metrics, thresholds and severity levels
&lt;br /&gt;- Path coverage
&lt;br /&gt;- JUnit wizards
&lt;br /&gt;- Auto-generated proxy code to test private methods
&lt;br /&gt;- Support for DbUnit and HTTPUnit
&lt;br /&gt;- Prevent compilation if code exceeds metric thresholds
&lt;br /&gt;- Metric violation notification
&lt;br /&gt;- Generate HTML or XML reports
&lt;br /&gt;- Supports JDK 1.4, 5 and 6&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/codign-coview"&gt;more about Codign CoView&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Convergence</title>
      <link>https://javatoolbox.com/tools/convergence</link>
      <guid>https://javatoolbox.com/tools/convergence</guid>
      <pubDate>Tue, 15 Mar 2005 03:09:34 GMT</pubDate>
      <description>&lt;p&gt;Quality management dashboard that enables tracking of application quality early in the software development life-cycle.
&lt;br /&gt;&lt;br /&gt;With Convergence, teams can:
&lt;br /&gt;- Determine if new code is being unit tested
&lt;br /&gt;- Track and understand code growth with respect to test coverage
&lt;br /&gt;- Identify areas to focus on to detect defects
&lt;br /&gt;- Identify the cause of test failures
&lt;br /&gt;- Uncover practices that impair maintainability and increase risk
&lt;br /&gt;&lt;br /&gt;Unlike static build reports, which convey limited information, Convergence tracks and relates multiple data points, enabling teams to understand and report on application quality through a unified focus on:
&lt;br /&gt;- NUnit/JUnit test statuses, code coverage and outputs
&lt;br /&gt;- Source code and code changes in CM systems like CVS and Subversion
&lt;br /&gt;- Assembly/package and class dependencies
&lt;br /&gt;- Code size, code audits, complexity and coupling
&lt;br /&gt;- NUnit/JUnit test &amp;amp; defect report relationships in defect tracking systems like JIRA and Bugzilla&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/convergence"&gt;more about Convergence&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rational PurifyPlus</title>
      <link>https://javatoolbox.com/tools/rational-purifyplus</link>
      <guid>https://javatoolbox.com/tools/rational-purifyplus</guid>
      <pubDate>Thu, 31 Mar 2005 00:02:12 GMT</pubDate>
      <description>&lt;p&gt;Set of automated runtime analysis tools for improving Linux-, UNIX- and Windows-based application reliability and performance.
&lt;br /&gt;Designed for Java, C, C++, and .NET applications.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Runtime and memory management error detection: memory corruption and leak detection.
&lt;br /&gt;- Application performance profiling: highlights application performance bottlenecks.
&lt;br /&gt;- Code coverage analysis: identifies untested code.
&lt;br /&gt;- Instruments code at the byte or object level.
&lt;br /&gt;- Server-side Java support: install PurifyPlus on your Web server to analyze Java Server Pages (JSP) and servlets.
&lt;br /&gt;- For software developers working with Java, Visual C++ and all VS.NET managed languages (including C# and VB.NET).
&lt;br /&gt;- Runs directly inside WebSphere Studio, Eclipse or Visual Studio, as well as stand-alone.
&lt;br /&gt;- Selective instrumentation: allows you to select which modules of an application to analyze.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/rational-purifyplus"&gt;more about Rational PurifyPlus&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JCover</title>
      <link>https://javatoolbox.com/tools/jcover</link>
      <guid>https://javatoolbox.com/tools/jcover</guid>
      <pubDate>Mon, 29 Aug 2005 19:16:19 GMT</pubDate>
      <description>&lt;p&gt;Code coverage analyser for Java programs.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;* User interface
&lt;br /&gt;* Statement and branch coverage
&lt;br /&gt;* Source as well as class files
&lt;br /&gt;* Client and server-side testing
&lt;br /&gt;* Coverage comparison
&lt;br /&gt;* Coverage differencing
&lt;br /&gt;* Reports and charts
&lt;br /&gt;* Coverage API for better control
&lt;br /&gt;* Batch mode for automated build&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jcover"&gt;more about JCover&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>