particle-os/debian-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge/test/data
History
Christian Kellner 818daef6cb test/stages: metadata checks for the rpm stage 
Use the new metadata checking capability of the stage tests to
check the metadata set by the rpm stage.
2020-08-13 10:50:34 +02:00
..
manifests test/assembler: check for ostree version metadata 2020-08-12 08:08:17 +02:00
os-release test: convert os-release-tests to test-data 2020-05-13 14:26:05 +02:00
scripts test/data: add mount_flags.py helper script 2020-08-12 16:52:27 +02:00
sources/org.osbuild.files test: make source-tests relative to ./test/data/ 2020-06-05 09:27:40 +02:00
stages test/stages: metadata checks for the rpm stage 2020-08-13 10:50:34 +02:00
README.md test/data: add mount_flags.py helper script 2020-08-12 16:52:27 +02:00

README.md

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 the os-release parser. The directory contains example os-release files (see os-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 have base as part of their name, they include a base set of packages which we very loosely define as @core plus the packages our test-suite needs. If they have build as part of their name, they have a very restricted package set which includes just what is needed in a build-root for osbuild. The fedora prefix is used for manifests that are kept up to date to the newest fedora release, and thus do not expose a specific f30, f32, etc. behavior.

    The rhel prefix is used for Red Hat Enterprise Linux images. Since they are not available publicly, the test-suite usually skips them.

    The filesystem manifest is used to test assemblers. These tests doesn't need a big filesystem tree representing a whole operating system. Instead, this manifest's tree is constructed just from the filesystem package and is marked using the selinux stage.

    Manifests prefixed with mpp-* are fed through the ManifestPreProcessors and then stored in the same directory with the mpp-* prefix dropped. The generated files are committed to the repository. Nevertheless, if you need to regenerate them, use make 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 attached sources.json.

  • scripts: This directory contains scripts used from other tests, i.e. although they are executables they are at the same time test-data to the actual (unit) tests.