This manual documents the standard procedures used to test PVC before release. This is a living document and will change frequently as new features are added and new corner cases are found.
As PVC does not currently feature any sort of automated tests, this is the primary way of ensuring functionality is as expected and the various components are operating correctly.
## Basic Tests
### Hypervisors
0. Stop then start all PVC node daemons sequentially, ensure they start up successfully.
0. Observe primary coordinator migration between nodes during startup sequence.
0. Verify reachability of floating IPs on each node across primary coordinator migrations.
0. Manually shuffle primary coordinator between nodes and verify as above (`pvc node primary`).
0. Automatically shuffle primary coordinator between nodes and verify as above (`pvc node secondary`).
### Virtual Machines
0. Deploy a new virtual machine using `vminstall` using managed networking and storage.
0. Start the VM on the first node, verify reachability over managed network (`pvc vm start`).
0. Verify console logs are operating (`pvc vm log -f`).
