Oracle Problem in Test Execution

by Nataliia Vasylyna | January 30, 2012 10:00 am

Checking of the result is a complex task, because of the theoretical difficulties and practical limitations. According to the long standing theoretical outputs result checking for software testing in common is an insoluble trouble.

To put it differently, there is no algorithmic or entirely automated solution to the common test oracle problem.

From the practical point of view, the expected behavior is hard to describe exactly so that the monitored behavior can be compared against. Software can fail in countless variations. The unexpected behavior may occur in really unexpected ways, making result checking complicated or almost unrealizable.

Nevertheless, there are cases where specific kinds of system failures, such as irresponsive behavior or system crash, are easy to detect.

Let’s try to find a rough solution to the oracle problem:

Learn more from QATestLab

Related Posts:

Endnotes:
  1. defect: https://blog.qatestlab.com/2011/10/11/main-types-of-defects-in-software-testing/
  2. How to prepare for Winter Sales: https://blog.qatestlab.com/2021/11/11/winter_sales_preparation/
  3. What is Data Migration Testing: https://blog.qatestlab.com/2021/08/11/what-is-data-migration-testing/
  4. Software Bugs Monthly Digest – July 2021: https://blog.qatestlab.com/2021/08/04/software-bugs-monthly-digest-july-2021/

Source URL: https://blog.qatestlab.com/2012/01/30/the-oracle-problem-in-the-test-execution/