Move the `test_boot` suite into ./test/run closer to the other runtime tests, and convert the used manifest over to an MPP based F32 manifest.
1.7 KiB
OSBuild Test Data
This directory contains data used by the osbuild test-suite. Since many formats do not allow comments, this file shortly describes their purpose.
Directories
-
./os-release/: This directory is consumed by the unit-tests of theos-releaseparser. The directory contains example os-release files (seeos-release(5)). Their directory name is the expected output of the parser. -
./manifests/: This directory contains osbuild manifests used throughout the test-suite.Manifests prefixed with
f30,f31, etc. are manifests that produce fedora images. If they havebaseas part of their name, they include a base set of packages which we very loosely define as@coreplus the packages our test-suite needs. If they havebuildas part of their name, they have a very restricted package set which includes just what is needed in a build-root for osbuild. Thefedoraprefix is used for manifests that are kept up to date to the newest fedora release, and thus do not expose a specificf30,f32, etc. behavior.The
rhelprefix is used for Red Hat Enterprise Linux images. Since they are not available publicly, the test-suite usually skips them.Manifests prefixed with
mpp-*are fed through the ManifestPreProcessors and then stored in the same directory with thempp-*prefix dropped. The generated files are committed to the repository. Nevertheless, if you need to regenerate them, usemake test-data. -
./sources/: This directory contains test-data for runtime tests of the source-engines. It contains a directory that is served via HTTP in the tests, and a directory of test-cases what to expect when using the attachedsources.json.