A controlled experiment on white-box database testing

Authors:
Javier Tuya;Javier Dolado;Ma Jose Suarez-Cabal;Claudio de la Riva
Affiliations:
University of Oviedo, Spain;University of the Basque Country, Spain;University of Oviedo, Spain;University of Oviedo, Spain
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
2008

Citing 8
Cited 0

A Fortran language system for mutation-based software testing

Software—Practice & Experience
Reviewing 25 Years of Testing Technique Experiments

Empirical Software Engineering
Using an SQL coverage measurement for testing database applications

Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Semantic errors in SQL queries: A quite complete list

Journal of Systems and Software - Special issue: Quality software
Mutating database queries

Information and Software Technology
SQLMutation: A tool to generate mutants of SQL database queries

MUTATION '06 Proceedings of the Second Workshop on Mutation Analysis
Use of Psychological Experimentation as an Aid to Development of a Query Language

IEEE Transactions on Software Engineering
Effects of query complexity and learning on novice user query performance with conceptual and logical database interfaces

IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans

Quantified Score

Hi-index	0.00

Visualization

Abstract

Controlled experiments are a powerful way to assess and compare the effectiveness of different techniques. In this paper we present the experimental results of the evaluation of the effectiveness of a structural test coverage criterion developed for SQL queries when used by a tester to guide the selection of database test cases. We describe a controlled experiment designed for comparing this criterion with other conventional criteria such as equivalence partitioning and boundary value analysis. The results show that 1) the use of the structural coverage allows the tester to develop more effective test cases, 2) the effectiveness is higher when considering the kind of faults that are more specifically related to SQL than other kinds of faults, and 3) the results give us some insight into how to improve the coverage criterion.