| |||||||||||||
Automatically shrinking the recipe generated by fuzz testing.Automatically shrinking the recipe generated by fuzz testing.Posted Nov 10, 2010 7:32 UTC (Wed) by gmatht (guest, #58961)Parent article: Jones: system call abuse
I fuzzed tested the LyX project with a tool I call Keytest. This randomly generates key-presses and feed them to the GUI under test until it gets a crash. Once it gets a crash it discards key-presses not required to reproduce the bug, to produce a small recipe. This recipe can be sent to the developer and manually reproduced, or used to quickly run an automated bisect to pin down a regression. I would have thought that another fuzz testing tool would also refine the recipes it outputs, but I haven't found this in any published feature lists. Has anyone come across this feature elsewhere? Also, would this feature be useful for testing the kernel, or is it usually the single last syscall that causes the problem?
(Log in to post comments)
Automatically shrinking the recipe generated by fuzz testing. Posted Nov 10, 2010 16:37 UTC (Wed) by JoeBuck (subscriber, #2330) [Link] These kinds of approaches (constrained random simulation, constraint solving, extraction of test cases that produce failures) are standard in hardware verification.
|
|||||||||||||