diff options
author | Michael Roth <mdroth@linux.vnet.ibm.com> | 2012-02-21 21:05:07 -0600 |
---|---|---|
committer | Andreas Färber <afaerber@suse.de> | 2012-06-08 16:11:14 +0200 |
commit | 2d496105397b8eca905f9a53c40e2faaac7bfa6b (patch) | |
tree | d673d90c95f09c24e6fb0f6ab6ee6014c447490f /qapi | |
parent | 4e27e819bea0ea6c8108dc7e9fa48afd6ec13c46 (diff) | |
download | qemu-2d496105397b8eca905f9a53c40e2faaac7bfa6b.zip qemu-2d496105397b8eca905f9a53c40e2faaac7bfa6b.tar.gz qemu-2d496105397b8eca905f9a53c40e2faaac7bfa6b.tar.bz2 |
qapi: Unit tests for visitor-based serialization
Currently we test our visitors individually, and seperately for input
vs. output. This is useful for validating internal representations
against the native C types and vice-versa, and other visitor-specific
testing, but it doesn't cover the potential use-case of using visitor
pairs for serialization/deserialization very well, and makes it
hard to easily extend the coverage for different C types / boundary
conditions.
To cover that we add a set of unit tests that takes a number of native C
values, passes them into an output visitor, extracts the values with an
input visitor, then compares the result to the original.
Plugging in new visitors to the test harness only requires a user to
implement the SerializeOps interface and add it to a list.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
Diffstat (limited to 'qapi')
0 files changed, 0 insertions, 0 deletions