diff options
| author | Eric Blake <eblake@redhat.com> | 2015-05-04 09:05:03 -0600 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2015-05-05 18:39:00 +0200 |
| commit | ad11dbb93752ffd4bd1d5f31da7e2d9c40a68e8a (patch) | |
| tree | 92f68f5ecf754fbb244cb4a258e56c1f2fcc5957 /tests/qapi-schema/enum-max-member.json | |
| parent | fe2a9303c9e511462f662a415c2e9d2defe9b7ca (diff) | |
qapi: Add some enum tests
Demonstrate that the qapi generator doesn't deal well with enums
that aren't up to par. Later patches will update the expected
results as the generator is made stricter.
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'tests/qapi-schema/enum-max-member.json')
| -rw-r--r-- | tests/qapi-schema/enum-max-member.json | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/qapi-schema/enum-max-member.json b/tests/qapi-schema/enum-max-member.json new file mode 100644 index 0000000000..1519541344 --- /dev/null +++ b/tests/qapi-schema/enum-max-member.json @@ -0,0 +1,3 @@ +# FIXME: we should reject user-supplied 'max' for clashing with implicit enum end +# TODO: should we instead munge the implicit value to avoid the clash? +{ 'enum': 'MyEnum', 'data': [ 'max' ] } |