ACM Home Page
Please provide us with feedback. Feedback
A survey of coverage based testing tools
Full text PdfPdf (71 KB)
Source International Conference on Software Engineering archive
Proceedings of the 2006 international workshop on Automation of software test table of contents
Shanghai, China
SESSION: Tools and environments table of contents
Pages: 99 - 103  
Year of Publication: 2006
ISBN:1-59593-408-1
Authors
Qian Yang  Avaya Labs Research, Basking Ridge, NJ
J. Jenny Li  Avaya Labs Research, Basking Ridge, NJ
David Weiss  Avaya Labs Research, Basking Ridge, NJ
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 40,   Downloads (12 Months): 197,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1138929.1138949
What is a DOI?

ABSTRACT

Test coverage is sometimes used as a way to measure how thoroughly software is tested. Coverage is used by software developers and sometimes by vendors to indicate their confidence in the readiness of their software. This survey studies and compares 17 coverage-based testing tools focusing on, but not restricted to coverage measurement. We also survey additional features, including program prioritization for testing, assistance in debugging, automatic generation of test cases, and customization of test reports. Such features make tools more useful and practical, especially for large-scale, real-life commercial software applications. Our initial motivations were both to understand the available test coverage tools and to compare them to a tool that we have developed, called eXVantage1 (a tool suite that includes code coverage testing, debugging, performance profiling, and reporting). Our study shows that each tool has its unique features tailored to its application domains. Therefore this study can be used to pick the right coverage testing tools depending on various requirements.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Yang, M. C. K.; Chao, A. Reliability-estimation and stopping-rules for software testing, based on repeated appearances of bugs; IEEE Transactions on Reliability, vol.44, no.2, p. 315--21, 1995.
 
3
Agitar (http://www.agitar.com/)
 
4
Avaya eXvantag (http://www.research.avayalabs.com/user/jjli/eXVantage.htm)
 
5
BullseyeCoverage (http://www.bullseye.com/index.html)
 
6
Clover (http://www.cenqua.com/clover/)
 
7
Cobertura (http://cobertura.sourceforge.net/)
 
8
CodeTest (http://www.metrowerks.com/MW/Develop/AMC/CodeTEST/default.htm)
 
9
Dynamic, DMS (http://dynamic-memory.com/)
 
10
gcov (http://gcc.gnu.org/onlinedocs/gcc-3.0/gcc_8.html)
 
11
Parasoft Insure ++ (http://www.parasoft.com/jsp/products/home.jspproduct=Insure&itemId=63)
 
12
Intel code coverage tool(http://www.intel.com/cd/software/products/asmo-na/eng/219794.htm)
 
13
JCover (http://www.mmsindia.com/JCover.html)
 
14
Koalog (http://www.koalog.com/php/kover.php)
 
15
Parasoft Jtest (http://parasoft.com/jsp/home.jsp)
 
16
Purify Plus (http://www-306.ibm.com/software/awdtools/purifyplus/)
 
17
Semantic Designs (http://www.semdesigns.com/index.html)
 
18
TCAT (http://www.evalidator.org/TestWorks/)
19
 
20
 
21
EMMA (http://emma.sourceforge.net/)
 
22
I. D. Baxter, Branch Coverage for Arbitrary Languages Made Easy(http://www.semanticdesigns.com/Company/Publications/TestCoverage.pdf)
 
23



REVIEW

"Timothy R. Hopkins : Reviewer"

The authors use this paper to showcase their test coverage tool, eXVantage. In addition, however, they provide a comparative overview of 17 open source and commercial test coverage tools. While these tools also implement a wide variety of other fe  more...

Collaborative Colleagues:
Qian Yang: colleagues
J. Jenny Li: colleagues
David Weiss: colleagues