Does code coverage provide a good stopping rule for operational profile based testing?

Breno Miranda, Antonia Bertolino

International Workshop on Automated Software Test (AST 2016), pp. 22–28, 2016.

Abstract

We introduce a new coverage measure, called the operational coverage, which is customized to the usage profile (count spectrum) of the entities to be covered. Operational coverage is proposed as an adequacy criterion for operational profile based testing, i.e., to assess the thoroughness of a black box test suite derived from the operational profile. To validate the approach we study the correlation between operational coverage of branches, statements, and functions, and the probability that the next test input will not fail. On the three subjects considered, we observed a moderate correlation in all cases (except a low correlation for function coverage for one subject), and consistently better results than traditional coverage measure.

Reference

Breno Miranda and Antonia Bertolino. 2016. Does code coverage provide a good stopping rule for operational profile based testing?. In Proceedings of the 11th International Workshop on Automation of Software Test (AST '16). ACM, New York, NY, USA, 22-28. DOI: http://dx.doi.org/10.1145/2896921.2896934

Bibtex Entry

@inproceedings{MirandaBertolinoAST16,
 author = {Miranda, Breno and Bertolino, Antonia},
 title = {Does Code Coverage Provide a Good Stopping Rule for Operational Profile Based Testing?},
 booktitle = {Proceedings of the 11th International Workshop on Automation of Software Test},
 year = {2016},
 pages = {22--28},
 doi = {10.1145/2896921.2896934},
 publisher = {ACM}
}

Download PDF
View electronic edition via DOI