Generic and Effective Specification of Structural Test Objectives

  • Michael Marcozzi
  • , Mickael Delahaye
  • , Sebastien Bardin
  • , Nikolai Kosmatov
  • , Virgile Prevosto

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

Abstract

A large amount of research has been carried out to automate white-box testing. While a wide range of different and sometimes heterogeneous code-coverage criteria have been proposed, there exists no generic formalism to describe them all, and available test automation tools usually support only a small subset of them. We introduce a new specification language, called HTOL (Hyperlabel Test Objectives Language), providing a powerful generic mechanism to define a wide range of test objectives. HTOL comes with a formal semantics, and can encode all standard criteria but full mutations. Besides specification, HTOL is appealing in the context of test automation as it allows handling criteria in a unified way.

Original languageEnglish
Title of host publicationProceedings - 10th IEEE International Conference on Software Testing, Verification and Validation, ICST 2017
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages436-441
Number of pages6
ISBN (Electronic)9781509060313
DOIs
Publication statusPublished - 15 May 2017
Externally publishedYes
Event10th IEEE International Conference on Software Testing, Verification and Validation, ICST 2017 - Tokyo, Japan
Duration: 13 Mar 201717 Mar 2017

Publication series

NameProceedings - 10th IEEE International Conference on Software Testing, Verification and Validation, ICST 2017

Conference

Conference10th IEEE International Conference on Software Testing, Verification and Validation, ICST 2017
Country/TerritoryJapan
CityTokyo
Period13/03/1717/03/17

Keywords

  • Coverage Criteria
  • MCDC
  • Test Objective Specification Language
  • White-Box Testing

Fingerprint

Dive into the research topics of 'Generic and Effective Specification of Structural Test Objectives'. Together they form a unique fingerprint.

Cite this