caca553a8f
This is to avoid any confusion with the Compose struct in the store, which contains the pinned rpmmd data and the pipeline, among other things. The struct in the test cases represent the user input to the compose route, so rename it 'compose-request', to make that clearer. Signed-off-by: Tom Gundersen <teg@jklm.no> |
||
|---|---|---|
| .. | ||
| cases | ||
| cloud-init | ||
| keyring | ||
| f27-build-from-ubuntu1804.json | ||
| README.md | ||
| run | ||
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-builddnf -y builddep golang-github-osbuild-composer.specmake rpmto build the software under testdnf install output/x86_64/golang-github-osbuild-composer-*.rpm- this will install both osbuild-composer, its -debuginfo, -debugsource and -tests packagessystemctl start osbuild-composer/usr/libexec/tests/osbuild-composer/osbuild-teststo 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 undercmd/./osbuild-tests- will execute the freshly built integration test suite