qemu/docs/image-fuzzer.txt

27 Test images are generated from scratch and have valid inner structure with some
31 Test runner
34 The test runner generates test images, executes tests utilizing generated
35 images, indicates their results and collects all test related artifacts (logs,
36 core dumps, test images, backing files).
37 The test means execution of all available commands under test with the same
38 generated test image.
39 By default, the test runner generates new tests and executes them until
40 keyboard interruption. But if a test seed is specified via the '--seed' runner
41 parameter, then only one test with this seed will be executed, after its finish
44 The runner uses an external image fuzzer to generate test images. An image
45 generator should be specified as a mandatory parameter of the test runner.
49 The runner activates generation of core dumps during test executions, but it
51 For comprehensive test results, please, set up your test environment
54 Paths to binaries under test (SUTs) ``qemu-img`` and ``qemu-io`` are retrieved
70 The runner accepts a list of commands under test as a JSON array via
75      /tmp/test ../qcow2
102 a single public API. See details in 'Test runner/image fuzzer' chapter of
120     of fields of this element will be fuzzed every test.
122     used. This case is useful for the test specialization.
125     will be always fuzzed for every test. This case is useful for regression
134 * Test runner/image fuzzer
136 The runner calls an image generator specifying the path to a test image file,
143 method that creates a test image, writes it to the specified file and returns
154 Random seed is set by the runner at every test execution for the regression
178     test images (image format description)
183 6.  Should generate the test image with the correct structure based on an image
189 10. Should accept a vector of actions as an argument (for test reproducing and
190     for test case specification, e.g. group of tests for header structure,
191     group of test for snapshots, etc)
197     of all possible test commands can be available in the test runner
199 14. Should support an external cancellation of a test run
201 16. All files related to a test result should be collected: a test image,
218 it makes the fuzzer itself invariant to an image format and test logic.
232 format, each of them will be fuzzed for the test image. It's a subset of
238 Test image is an output image of the fuzzer defined by the current seed and