Debugging without Testing

Wided Ghardallou, Nafi Diallo, Ali Mili, Marcelo F. Frias

Research output: Chapter in Book/Report/Conference proceedingConference contribution

7 Scopus citations

Abstract

It is so inconceivable to debug a program without testing it that these two words are used nearly interchangeably. Yet we argue that using the concept of relative correctness we can indeed remove a fault from a program and prove that the fault has been removed, by proving that the new program is more correct than the original. This is a departure from the traditional roles of proving and testing methods, whereby static proof methods are applied to a correct program to prove its correctness, and dynamic testing methods are applied to an incorrect program to expose its faults.

Original languageEnglish (US)
Title of host publicationProceedings - 2016 IEEE International Conference on Software Testing, Verification and Validation, ICST 2016
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages113-123
Number of pages11
ISBN (Electronic)9781509018260
DOIs
StatePublished - Jul 18 2016
Event9th IEEE International Conference on Software Testing, Verification and Validation, ICST 2016 - Chicago, United States
Duration: Apr 10 2016Apr 15 2016

Publication series

NameProceedings - 2016 IEEE International Conference on Software Testing, Verification and Validation, ICST 2016

Other

Other9th IEEE International Conference on Software Testing, Verification and Validation, ICST 2016
Country/TerritoryUnited States
CityChicago
Period4/10/164/15/16

All Science Journal Classification (ASJC) codes

  • Software
  • Safety, Risk, Reliability and Quality

Keywords

  • correctness
  • debugging
  • fault removal
  • faults
  • relative correctness
  • testing

Fingerprint

Dive into the research topics of 'Debugging without Testing'. Together they form a unique fingerprint.

Cite this