Downloads provided by UsageCounts
If we have a program for which neither code nor traces nor input samples nor input specifications are available, how can we generate test inputs? In this paper, we show that this is possible if the program provides failure feedback---that is, information on whether an input is valid or not, and whether the input can be considered a prefix of a valid input (i.e. incomplete) or not. Such feedback is available out of the box (or very easy to implement) for numerous input processors such as microprocessors, compilers, user interfaces, and off-the-shelf parsers. Given this feedback, we show that it is possible to quickly generate any input that will be accepted by the program, by systematically enumerating and testing input continuations. We have implemented our technique in a prototype called \decoder. In its evaluation on five subjects, decoder is effective and efficient even in comparison to instrumentation-based competition.
test case generation, software testing, blackbox testing, fuzzing
test case generation, software testing, blackbox testing, fuzzing
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
| views | 5 | |
| downloads | 2 |

Views provided by UsageCounts
Downloads provided by UsageCounts