qemu/tests/qapi-schema/data-member-array.out

[OrderedDict([('enum', 'abc'), ('data', ['a', 'b', 'c'])]),
 OrderedDict([('type', 'def'), ('data', OrderedDict([('array', ['abc'])]))]),
 OrderedDict([('command', 'okay'), ('data', OrderedDict([('member1', ['int']), ('member2', ['def'])]))])]
[{'enum_name': 'abc', 'enum_values': ['a', 'b', 'c']}]
[OrderedDict([('type', 'def'), ('data', OrderedDict([('array', ['abc'])]))])]
qapi: Add some type check tests Demonstrate that the qapi generator silently parses confusing types, which may cause other errors later on. Later patches will update the expected results as the generator is made stricter. Most of the new tests focus on blatant errors. But returns-whitelist is a case where we have historically allowed returning something other than a JSON object from particular commands; we have to keep that behavior to avoid breaking clients, but it would be nicer to avoid adding such commands in the future, because any return that is not an (array of) object cannot be easily extended if future qemu wants to return additional information. The QMP protocol already documents that clients should ignore unknown dictionary keys, but does not require clients to have to handle more than one type of JSON object. Signed-off-by: Eric Blake <eblake@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com> 2015-05-04 09:05:20 -06:00			`[OrderedDict([('enum', 'abc'), ('data', ['a', 'b', 'c'])]),`
			`OrderedDict([('type', 'def'), ('data', OrderedDict([('array', ['abc'])]))]),`
			`OrderedDict([('command', 'okay'), ('data', OrderedDict([('member1', ['int']), ('member2', ['def'])]))])]`
			`[{'enum_name': 'abc', 'enum_values': ['a', 'b', 'c']}]`
			`[OrderedDict([('type', 'def'), ('data', OrderedDict([('array', ['abc'])]))])]`