2014/11/20 by Earl T. Barr, Mark Harman, Phil McMinn +2 · 1,050 citations
Computer Science · #Computer science #Oracle #Programming language #Regression testing #Software #Software Engineering Research #Software Reliability and Analysis Research #Software Testing and Debugging Techniques #Software construction #Software development #Software engineering #Software performance testing #Software reliability testing #Software testing
paper · pdf · doi:10.1109/tse.2014.2372785
published in IEEE Transactions on Software Engineering 41(5), 507-525 (IEEE Computer Society)
openalex publication_date 2014/11/20 · openalex created_date 2025/10/10 · openalex updated_date 2026/08/01
Testing involves examining the behaviour of a system in order to discover potential faults. Given an input for a system, the challenge of distinguishing the corresponding desired, correct behaviour from potentially incorrect behavior is called the “test oracle problem”. Test oracle automation is important to remove a current bottleneck that inhibits greater overall test automation. Without test oracle automation, the human has to determine whether observed behaviour is correct. The literature on test oracles has introduced techniques for oracle automation, including modelling, specifications, contract-driven development and metamorphic testing. When none of these is completely adequate, the final source of test oracle information remains the human, who may be aware of informal specifications, expectations, norms and domain specific information that provide informal oracle guidance. All forms of test oracles, even the humble human, involve challenges of reducing cost and increasing benefit. This paper provides a comprehensive survey of current approaches to the test oracle problem and an analysis of trends in this important area of software testing research and practice.