Tools for coverage testing: necessary but not sufficient

Authors:
Chris Gaffney;Christian Trefftz;Paul Jorgensen
Affiliations:
Grand Valley State University, Allendale, Michigan;Grand Valley State University, Allendale, Michigan;Grand Valley State University, Allendale, Michigan
Venue:
Journal of Computing Sciences in Colleges
Year:
2004

Citing 4
Cited 1

Software Testing: A Craftman's Approach

Software Testing: A Craftman's Approach
JUnit in Action

JUnit in Action
Uprooting Software Defects at the Source

Queue - Instant Messaging
Object-Oriented and Classical Software Engineering

Object-Oriented and Classical Software Engineering

Experiences in coverage testing of a Java middleware

SEM '05 Proceedings of the 5th international workshop on Software engineering and middleware

Quantified Score

Hi-index	0.00

Visualization

Abstract

Testing is recognized as a fundamental part of Software Development. Tools for unit testing and coverage testing are becoming widely used; they are necessary, but not sufficient, to demonstrate that a piece of software works correctly. While various forms of path coverage are reported by coverage tools, a tester cannot rely only on this. Two simple functions are used to illustrate this with JUnit and Clover. These examples should be useful in a classroom setting when discussing software testing techniques.