@conference {15435,
	title = {Faults{\textquoteright} context matters},
	booktitle = {Fourth international workshop on Software quality assurance: in conjunction with the 6th ESEC/FSE joint meeting},
	series = {SOQUA {\textquoteright}07},
	year = {2007},
	month = {2007///},
	pages = {112 - 115},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When choosing a testing technique, practitioners want to know which one will detect the faults that matter most to them in the programs that they plan to test. Do empirical evaluations of testing techniques provide this information? More often than not, they report how many faults in a carefully chosen "representative" sample the evaluated techniques detect. But the population of faults that such a sample would represent depends heavily on the faults{\textquoteright} context or environment---as does the cost of failing to detect those faults. If empirical studies are to provide information that a practitioner can apply outside the context of the study, they must characterize the faults studied in a way that translates across contexts. A testing technique{\textquoteright}s fault-detecting abilities could then be interpreted relative to the fault characterization. In this paper, we present a list of criteria that a fault characterization must meet in order to be fit for this task, and we evaluate several well-known fault characterizations against the criteria. Two families of characterizations are found to satisfy the criteria: those based on graph models of programs and those based on faults{\textquoteright} detection by testing techniques.},
	isbn = {978-1-59593-724-7},
	doi = {10.1145/1295074.1295096},
	url = {http://doi.acm.org/10.1145/1295074.1295096},
	author = {Strecker,Jaymie and Memon, Atif M.}
}
