lorax/test/run

#!/bin/sh -e
# This is the expected entry point for Cockpit CI; will be called without
# arguments but with an appropriate $TEST_OS, and optionally $TEST_SCENARIO

make vm

if [ -n "$TEST_SCENARIO" ]; then
  if [ "$TEST_SCENARIO" == "lorax" ]; then
    test/check-lorax TestLorax
  fi
else
  test/check-cli TestImages
fi
Use Cockpit's test images and infrastructure Allows to run the tests on multiple operating systems and on the infrastructure that the Cockpit team maintains. `make vm` downloads one of Cockpit's test images (override which one with TEST_OS) and installs rpms build from the local checkout of lorax. The resulting image is placed in `test/images/$TEST_OS`. TEST_OS can be set to any of Cockpit's supported images (default: fedora-30). Run `make check-vm` to run the CLI checks in the VM. The bulk of the work is done in `test/check-cli`, which uses Cockpit's `bots` library to start the VM and run the script in it. Also included is a `test/run` script, which is the entrypoint for Cockpit's test infrastructure. 2019-04-12 18:17:28 +00:00			`#!/bin/sh -e`
			`# This is the expected entry point for Cockpit CI; will be called without`
			`# arguments but with an appropriate $TEST_OS, and optionally $TEST_SCENARIO`

			`make vm`

			`if [ -n "$TEST_SCENARIO" ]; then`
tests: Disable non-cli test scenarios b/c osbuild-composer the image building functionality is now tested by the osbuild-composer test suite. We weren't successfull at making this test suite work with the 2 backends so decided to disabled these scenarios instead. In the future they will likely be deleted. 2020-07-21 08:28:15 +00:00			`if [ "$TEST_SCENARIO" == "lorax" ]; then`
tests: Add a lorax boot.iso test This builds a boot.iso in the vm, copies it out, and boots it. The tests that run inside the boot.iso (/tests/lorax/test_boot_bootiso.sh) cannot use beakerlib so it needs to be a simple shell script returning 1 on failure along with a descriptive message. 2019-11-04 19:28:54 +00:00			`test/check-lorax TestLorax`
Split live-iso and qcow2 and update test scenario execution this makes it possible to have more granular test execution reported as separate statuses on GitHub. ATM we will have: - cockpit/fedora-30 - cockpit/fedora-30/live-iso - cockpit/fedora-30/qcow2 - cockpit/fedora-30/aws - cockpit/fedora-30/azure - cockpit/fedora-30/openstack - cockpit/fedora-30/vmware 2019-05-29 08:30:10 +00:00			`fi`
Use Cockpit's test images and infrastructure Allows to run the tests on multiple operating systems and on the infrastructure that the Cockpit team maintains. `make vm` downloads one of Cockpit's test images (override which one with TEST_OS) and installs rpms build from the local checkout of lorax. The resulting image is placed in `test/images/$TEST_OS`. TEST_OS can be set to any of Cockpit's supported images (default: fedora-30). Run `make check-vm` to run the CLI checks in the VM. The bulk of the work is done in `test/check-cli`, which uses Cockpit's `bots` library to start the VM and run the script in it. Also included is a `test/run` script, which is the entrypoint for Cockpit's test infrastructure. 2019-04-12 18:17:28 +00:00			`else`
Split live-iso and qcow2 and update test scenario execution this makes it possible to have more granular test execution reported as separate statuses on GitHub. ATM we will have: - cockpit/fedora-30 - cockpit/fedora-30/live-iso - cockpit/fedora-30/qcow2 - cockpit/fedora-30/aws - cockpit/fedora-30/azure - cockpit/fedora-30/openstack - cockpit/fedora-30/vmware 2019-05-29 08:30:10 +00:00			`test/check-cli TestImages`
Use Cockpit's test images and infrastructure Allows to run the tests on multiple operating systems and on the infrastructure that the Cockpit team maintains. `make vm` downloads one of Cockpit's test images (override which one with TEST_OS) and installs rpms build from the local checkout of lorax. The resulting image is placed in `test/images/$TEST_OS`. TEST_OS can be set to any of Cockpit's supported images (default: fedora-30). Run `make check-vm` to run the CLI checks in the VM. The bulk of the work is done in `test/check-cli`, which uses Cockpit's `bots` library to start the VM and run the script in it. Also included is a `test/run` script, which is the entrypoint for Cockpit's test infrastructure. 2019-04-12 18:17:28 +00:00			`fi`