Specification test coverage adequacy criteria = specification test generation inadequacy criteria

  • Authors:

  • Mats P. E. Heimdahl;Devaraj George;Robert Weber

  • Affiliations:

  • Department of Computer Science and Engineering, University of Minnesota;Department of Computer Science and Engineering, University of Minnesota;Department of Computer Science and Engineering, University of Minnesota

  • Venue:
  • HASE'04 Proceedings of the Eighth IEEE international conference on High assurance systems engineering
  • Year:
  • 2004

Quantified Score

Hi-index 0.00

Visualization

Abstract

The successful analysis technique model checking can be employed as a test-case generation technique to generate tests from formal models. When using a model checker for test case generation, we leverage the witness (or counterexample) generation capability of model-checkers for constructing test cases. Test criteria are expressed as temporal properties and the witness traces generated for these properties are instantiated to create complete test sequences, satisfying the criteria. In this report we describe an experiment where we investigate the fault finding capability of test suites generated to provide three specification coverage metrics proposed in the literature (state, transition, and decision coverage). Our findings indicate that although the coverage may seem reasonable to measure the adequacy of a test suite, they are unsuitable when used to generate test suites. In short, the generated test sequences technically provide adequate coverage, but do so in a way that tests only a small portion of the formal model. We conclude that automated testing techniques must be pursued with great caution and that new coverage criteria targeting formal specifications are needed.