libvirt/tests/virnetdaemondata
Erik Skultety 4ac0d545e8 test: Replace tabs with spaces in virnetdaemondata json files
JSON data that are used to initialize tests in virnetdaemontest should
be in a consistent format, i.e. not using tabs for indentation, those
should be replaced by spaces.
2015-08-24 09:30:40 +02:00
..
input-data-admin-nomdns.json test: Replace tabs with spaces in virnetdaemondata json files 2015-08-24 09:30:40 +02:00
input-data-anon-clients.json
input-data-initial-nomdns.json
input-data-initial.json
input-data-no-keepalive-required.json test: Replace tabs with spaces in virnetdaemondata json files 2015-08-24 09:30:40 +02:00
output-data-admin-nomdns.json rpc: Remove keepalive_required option 2015-08-10 13:15:56 +02:00
output-data-anon-clients.json rpc: Remove keepalive_required option 2015-08-10 13:15:56 +02:00
output-data-initial-nomdns.json rpc: Remove keepalive_required option 2015-08-10 13:15:56 +02:00
output-data-initial.json rpc: Remove keepalive_required option 2015-08-10 13:15:56 +02:00
output-data-no-keepalive-required.json test: Replace tabs with spaces in virnetdaemondata json files 2015-08-24 09:30:40 +02:00
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.