Results 1 -
2 of
2
Oracles are Hardly Attain’d, And Hardly Understood: Confessions of Software Testing Researchers
- THE SYMPOSIUM ON ENGINEERING TEST HARNESS (TSETH '13), IN PROCEEDINGS OF THE 13TH INTERNATIONAL CONFERENCE ON QUALITY SOFTWARE (QSIC '13)
, 2013
"... In software testing, a test oracle refers to the mechanism for determining whether the results of the software under test agree with the expected outcomes. To achieve this, we need a means to determine the expected outcomes, a means to gauge the actual results, and a means to decide whether the actu ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
In software testing, a test oracle refers to the mechanism for determining whether the results of the software under test agree with the expected outcomes. To achieve this, we need a means to determine the expected outcomes, a means to gauge the actual results, and a means to decide whether the actual results agree with the expected outcomes. In real-life situations, however, a test oracle may not exist owing to a missing link in any of these aspects. In this paper, we summarize our research for the last 15 years on selected issues related to each of these aspects. We present the use of metamorphic testing, pattern classification, and formal object equivalence and nonequivalence to alleviate the problems.
©中国科学院软件研究所版权所有. Tel: +86-10-62562563 自动程序修复方法研究进展
"... Abstract: Automatic program repair helps developers reduce the cost of manual bug fixing. Approaches to test-suite based repair aims to generate code patches to pass the test suite as well as maintain the program execution. This paper reviews available literature on test-suite based repair and stat ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract: Automatic program repair helps developers reduce the cost of manual bug fixing. Approaches to test-suite based repair aims to generate code patches to pass the test suite as well as maintain the program execution. This paper reviews available literature on test-suite based repair and state the progress in two directions: approaches to automatic repair and empirical foundations. First, existing approaches to automatic repair are described into three categories, namely search based, exhaustion based, and constraint-solving based patch generation. Second, empirical foundations on repair are detailed, including the argumentation in the research field. Related techniques are then briefly introduced as the supplementation of program repair. Finally, opportunities and challenges are presented to summarize this review.
