The tests works by executing osbuild with predefined pipeline. Then the image boots and the testing script creates SSH connection to the running VM. If everything goes fine `systemctl is-system-running` is executed with result `running` and the test case passed. The JSON definition of the test case contains also a blueprint that should generate the desired pipeline, but it didn't work for me, so I'm including it for future use from the golang unit tests. |
||
|---|---|---|
| .. | ||
| ami_empty_blueprint.json | ||
| disk_empty_blueprint.json | ||
| ext4_empty_blueprint.json | ||
| fedora-30-cloud-base.json | ||
| openstack_empty_blueprint.json | ||
| qcow2_empty_blueprint.json | ||
| qcow2_local_boot.json | ||
| vhd_empty_blueprint.json | ||
| vmdk_empty_blueprint.json | ||