articleIEEE Transactions on Software EngineeringFeb 23, 2012Closed access

Whole Test Suite Generation

University of Sheffield · Saarland University · +1 more institution

Indexed incrossref

Abstract

Not all bugs lead to program crashes, and not always is there a formal specification to check the correctness of a software test's outcome. A common scenario in software testing is therefore that test data are generated, and a tester manually adds test oracles. As this is a difficult task, it is important to produce small yet representative test sets, and this representativeness is typically measured using code coverage. There is, however, a fundamental problem with the common approach of targeting one coverage goal at a time: Coverage goals are not independent, not equally difficult, and sometimes infeasible—the result of test generation is therefore dependent on the order of coverage goals and how many of…

Citation impact

580
total citations
FWCI
39.17
Percentile
100%
References
58
Citations per year

Authors

2

Topics & keywords

Keywords
  • Computer science
  • Test suite
  • Code coverage
  • Correctness
  • Test case
  • Test (biology)
  • Task (project management)
  • Source code
No related works found for this paper.