Saturation-based testing of concurrent programs

Elena Sherman, Matthew B. Dwyer, Sebastian Elbaum

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

29 Scopus citations

Abstract

Coverage measures help to determine whether a test suite exercises a program adequately according to a testing criterion. Many existing measures, however, are defined over coverage domains that cannot be precisely calculated, rendering them of limited value in assessing the extent of testing activities. To exploit the use of such measures, we formalize saturation-based test adequacy, a form of adequacy focused on the rate at which coverage increases during test suite execution. We define a family of coverage metrics for concurrent program testing that are well-suited to saturation-based adequacy and present a study that explores their cost and effectiveness. The results of this study suggest that saturation-based testing can serve as an effective complement to traditional notions of coverage-based testing.

Original languageEnglish
Title of host publicationESEC-FSE'09 - Proceedings of the Joint 12th European Software Engineering Conference and 17th ACM SIGSOFT Symposium on the Foundations of Software Engineering
Pages53-62
Number of pages10
DOIs
StatePublished - 2009
EventJoint 12th European Software Engineering Conference and 17th ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC-FSE'09 - Amsterdam, Netherlands
Duration: 24 Aug 200928 Aug 2009

Publication series

NameESEC-FSE'09 - Proceedings of the Joint 12th European Software Engineering Conference and 17th ACM SIGSOFT Symposium on the Foundations of Software Engineering

Conference

ConferenceJoint 12th European Software Engineering Conference and 17th ACM SIGSOFT Symposium on the Foundations of Software Engineering, ESEC-FSE'09
Country/TerritoryNetherlands
CityAmsterdam
Period24/08/0928/08/09

Keywords

  • Concurrent programs
  • Coverage
  • Test adequacy criteria

Fingerprint

Dive into the research topics of 'Saturation-based testing of concurrent programs'. Together they form a unique fingerprint.

Cite this