A Brief Survey on Oracle-based Test Adequacy Metrics

12/12/2022
by   Soneya Binta Hossain, et al.
0

Even though code coverage is a widespread and popular test adequacy metric, it has several limitations. One of the major limitations is that code coverage does not satisfy the necessary conditions for effective fault detection, as it only cares about executing different parts of a program. Studies showed that code coverage as a test adequacy metric is a poor indicator of the quality of a test suite as it does not consider the quality of test oracles. To address this limitation, researchers proposed extensions to traditional code coverage metrics that explicitly consider test oracle quality. We name these metrics as oracle-based code coverage. This survey paper has discussed all oracle-based techniques published so far, starting from 2007.

READ FULL TEXT

page 1

page 2

page 3

page 4

research
09/07/2020

Code Coverage Aware Test Generation Using Constraint Solver

Code coverage has been used in the software testing context mostly as a ...
research
04/20/2018

Ticket Coverage: Putting Test Coverage into Context

There is no metric that determines how well the implementation of a tick...
research
09/05/2023

Mind the Gap: The Difference Between Coverage and Mutation Score Can Guide Testing Efforts

An "adequate" test suite should effectively find all inconsistencies bet...
research
04/19/2022

Test suite effectiveness metric evaluation: what do we know and what should we do?

Comparing test suite effectiveness metrics has always been a research ho...
research
08/26/2021

Code Coverage and Test Automation: State of the Art

This chapter surveys the state of the art in code coverage from the pers...
research
11/28/2022

P4Testgen: An Extensible Test Oracle For P4

We present P4Testgen, a test oracle for the P4_16 language. P4Testgen su...

Please sign up or login with your details

Forgot password? Click here to reset