libvirt/tests/virnetdaemondata
Daniel P. Berrangé 72874b2d11 tests: validate private data / pre / post exec hooks for RPC APIs
Validate that the virNetServer(Client) RPC APIs are processing the
private data callbacks correctly by passing in non-NULL pointers.

Reviewed-by: John Ferlan <jferlan@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2018-02-02 13:00:48 +00:00
..
input-data-admin-nomdns.json
input-data-admin-server-names.json
input-data-anon-clients.json
input-data-client-auth-pending-failure.json
input-data-client-auth-pending.json
input-data-client-ids.json
input-data-client-timestamp.json
input-data-initial-nomdns.json
input-data-initial.json
input-data-no-keepalive-required.json
output-data-admin-nomdns.json
output-data-admin-server-names.json
output-data-anon-clients.json
output-data-client-auth-pending.json
output-data-client-ids.json
output-data-client-timestamp.json
output-data-initial-nomdns.json
output-data-initial.json
output-data-no-keepalive-required.json
README

   virnetservertest data files
   ===========================

The various input-data-*.json files are a record of all the historical
formats that libvirt has been able to produce data for. Everytime a
new field is added to the JSON output, a *new* input data file should
be created. We must not add new fields to existing input-data files,
nor must we ever re-structure them if code changes, as we must check
new code handles the legacy formats.

The various output-data-*.json files are the record of what the *new*
JSON output should look like for the correspondingly named input-data
file. It is permissible to change the existing output-data-*.json
files if the format we save in is updated.