particle-os/debian-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge/test/data
History
Tomáš Hozza c9639c41f9 Stages/rhsm: support setting 'auto_enable_yum_plugins' option 
Support setting the `auto_enable_yum_plugins` option in the `rhsm`
section of `rhsm.conf`.

Add a unit test for the stage schema and also adjust the stage test
manifest.

Related to: https://github.com/osbuild/images/issues/1408

Signed-off-by: Tomáš Hozza <thozza@redhat.com>
2025-04-10 12:29:21 +02:00
..
assemblers Test/assemblers: update manifest to use Fedora 40 2024-07-02 09:46:45 +02:00
certs test: regenerate X509 test certs 2024-11-22 10:15:50 +01:00
manifests test: generate container-dev-null test manifests 2025-01-17 10:10:47 +01:00
os-release util/osrelease.py: Replaced string stripping with shlex.split() 2024-12-04 14:54:00 -05:00
scripts test: container creation script with /dev/null 2025-01-17 10:10:47 +01:00
sources test: reformat json data to appease linter 2025-01-14 08:19:16 +01:00
spdx test/sbom/spdx: test using custom license index file 2025-02-27 13:31:19 +01:00
stages Stages/rhsm: support setting 'auto_enable_yum_plugins' option 2025-04-10 12:29:21 +02:00
testrepos data: include appstream repository metadata 2025-01-22 18:03:21 +01:00
README.md rename all .mpp.json files to .mpp.yaml 2023-08-08 12:41:17 +02:00
v2 test: Add skopeo tests 2022-02-10 14:43:17 +01: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 ending on .mpp.yaml are fed through the ManifestPreProcessors and then stored in the same directory with an .json extension (replacing .mpp.yaml). 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.