Java code coverage tools: Difference between revisions

Content deleted Content added
Godin (talk | contribs)
JaCoCo 0.8.4
this is not about websites and tools which report and collect code coverage statistics, but tools which actualle produce them. remove jtest, sonarqube
Line 157:
* The runtime overhead of added instrumentation is small (5–20%) and the bytecode instrumentor itself is very fast (mostly limited by file I/O speed). Memory overhead is a few hundred bytes per Java class.
* EMMA is 100% pure Java, has no external library dependencies, and works in any Java 2 JVM (even 1.2.x).
 
=== EMMA-based tools ===
 
* SonarQube EMMA plugin—Enables usage of EMMA analyses within the code quality management platform [[SonarQube]]
* [http://code.google.com/webtoolkit/tools/download-codepro.html Google CodePro AnalytiX]
* [https://wiki.jenkins-ci.org/display/JENKINS/Emma+Plugin Jenkins Emma Plugin]
 
== Jtest ==
{{Infobox Software
| name = Jtest
| developer = [[Parasoft]]
| released = {{Start date and age|1997}}
| latest_release_version = 10.3.3
| latest_release_date = {{Start date and age|2017|11|07}}
| genre = [[Code coverage]]
| language = English, Chinese, Japanese
| license = [[Proprietary software|Proprietary]] [[commercial software]]
| website = {{URL|https://www.parasoft.com/products/jtest/}}
}}
 
'''Jtest''' is an automated [[Java platform|Java]] [[software testing]] tool that is made by [[Parasoft]]. The product includes code coverage as well as other testing technologies such as [[Data-flow analysis]] [[Unit testing|Unit test-case generation and execution]], [[Static code analysis|static analysis]], [[regression testing]], and [[runtime error detection]].
<ref>[http://java.sys-con.com/read/299985.htm JDJ Product Review - Parasoft Jtest 8.0] by Jason Bell, Java Developers Journal (JDJ), November 17, 2006</ref>
 
Jtest can gather coverage from a variety of frameworks as well as types of testing including unit test, functional testing or manual testing. Through integration with [[Parasoft Concerto|Parasoft DTP]] the coverage from these different types of testing can be accurately merged to create a single coverage score.<ref>{{cite web|url=https://blog.parasoft.com/testing-123-change-based-testing-coverage |title=Testing 123 with Parasoft's Mark Lambert: Change-Based Testing and Merged Correlated Code Coverage|date=2016-12-01 |accessdate=2018-02-08}}</ref>
 
Jtest can be run from an eclipse-based GUI, command line mode, or integrated with [[Continuous integration|CI]] systems.
 
Advanced reporting and analytics are performed using Parasoft DTP and include capabilities for:
*[[Traceability|Test-to-code traceability]]
*[[Requirements traceability]]
*Merged coverage (from multiple runs or tools)
*Change-based testing - correlating which tests must be run based on code that changed
 
== Serenity ==