particle-os/debian-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
debian-forge/test/data/README.md
David Rheinsberg 6e8562f712 test: make source-tests relative to ./test/data/ 
This moves the `sources_tests` into ./test/data/sources/ and makes the
entire test use `locate_test_data()` to get relative paths for their
accesses.

This further improves our test cases to support running from
installments rather than local checkouts. We need access to ./test/data
guarded, so we can install packages and still have the tests access the
correct paths.

This also adjusts the HTTP-Server we use in the test to serve data
relative to a path it is handed. I now chose `./test/data`, which will
easily allow us to re-use the same HTTP-Server in the future for other
tests that require it.
2020-06-05 09:27:40 +02:00

1.6 KiB
Raw Blame History

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 rhel prefix 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 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.