History

Ondřej Budai 714f64bf22 tests: fail the tests if no manifest is given All the tests have a manifest, therefore there's no need for skipping a test.		2020-03-10 14:40:52 +01:00
..
cases	test/cases: test manifests rather than pipelines	2020-03-08 21:05:01 +01:00
cloud-init	test/run: pass cloud-init data to qemu	2019-12-10 02:47:35 +01:00
keyring	Introduce local boot test case for QCOW2	2019-11-11 15:47:01 +01:00
f27-build-from-ubuntu1804.json	pipeline: support osbuild runners	2019-11-27 02:47:36 +01:00
README.md	Add instructions how to install build-deps in test/README	2020-03-04 19:56:25 +01:00
run	tests: fail the tests if no manifest is given	2020-03-10 14:40:52 +01:00

README.md

osbuild-composer testing information

Integration testing

This will consume the osbuild-composer API surface via the composer-cli command line interface. Implementation is under cmd/osbuild-tests/.

The easiest way to get started with integration testing from a git checkout is:

dnf -y install rpm-build
dnf -y builddep golang-github-osbuild-composer.spec
make rpm to build the software under test
dnf install output/x86_64/golang-github-osbuild-composer-*.rpm - this will install both osbuild-composer, its -debuginfo, -debugsource and -tests packages
systemctl start osbuild-composer
/usr/libexec/tests/osbuild-composer/osbuild-tests to execute the test suite. It is best that you use a fresh system for installing and running the tests!

NOTE:

The easiest way to start osbuild-composer is via systemd because it takes care of setting up the UNIX socket for the API server.

If you are working on a pull request that adds more integration tests (without modifying osbuild-composer itself) then you can execute the test suite from the local directory without installing it:

make build - will build everything under cmd/
./osbuild-tests - will execute the freshly built integration test suite