]> git.proxmox.com Git - pve-cluster.git/commit
add simple corosync config parser self check
authorThomas Lamprecht <t.lamprecht@proxmox.com>
Mon, 26 Jun 2017 12:10:57 +0000 (14:10 +0200)
committerDietmar Maurer <dietmar@proxmox.com>
Tue, 27 Jun 2017 05:02:20 +0000 (07:02 +0200)
commitf779187a7b85809d19fc6ccf6766144674d3a6b4
tree1f9a8dbfe626e3ccc5fe087289914281f1a2a7ec
parentaaf9126fe648068ea86ec9ef5a131746630c36a5
add simple corosync config parser self check

Each test reads and parses a config "writes" it again and then
re-parses it.
Then both the parsed hash structures and the raw config get compared
This is cheap and should catch simple regressions in either the
parser or writer, as currently we have no safety net that
modifications on either one didn't cause regressions.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
data/Makefile.am
data/test/Makefile [new file with mode: 0644]
data/test/corosync_configs/multiple-nodes.conf [new file with mode: 0644]
data/test/corosync_configs/single-node.conf [new file with mode: 0644]
data/test/corosync_parser_test.pl [new file with mode: 0755]