keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
e35f867494
rpm-ostree/tests
History
Colin Walters 366826132a libpriv: Rename "unpacker" to "importer", split off "unpacker-core" 
In the jigdo path we don't actually want to import the OIRPM literally
into ostree.  I considered adding jigdo logic into `rpmostree-unpacker.c`
but it'd be a mess as the functionality is quite logically separate
from importing.

So split off an `unpacker-core.c` file which has the bare libarchive+RPM
helpers, and rename `RpmOstreeUnpacker` to `RpmOstreeImporter`.

Closes: #1110
Approved by: jlebon
2017-11-20 20:57:33 +00:00
..
check libpriv: Rename "unpacker" to "importer", split off "unpacker-core" 2017-11-20 20:57:33 +00:00
common libvm: factor out helpers to start httpd 2017-10-13 15:00:25 +00:00
compose-tests compose: Do relabel before downloading in --ex-unified-core 2017-11-20 15:35:21 +00:00
composedata postprocess: Use names (not ids) in synthesized tmpfiles.d files 2017-10-27 19:46:26 +00:00
ex-container-tests core: Don't try to apply non-root uid/gid when run as non-root 2017-11-17 18:59:34 +00:00
gpghome daemon: start with one commit only when resolving versions 2016-12-24 12:28:48 +00:00
manual db: Remove query parameter to diff 2015-04-23 16:30:18 -04:00
utils daemon: Add a sanitycheck(/bin/true) before we deploy a tree 2017-07-27 17:58:58 +00:00
vmcheck unpacker: Error out when trying to install RPM in /usr/local 2017-11-08 03:56:20 +00:00
compose Add test infra for ex container, and one test for bash 2017-10-02 18:04:24 +00:00
ex-container tests/ex-container: Disable parallelism for now 2017-11-17 18:59:34 +00:00
README.md tests: Add ./tests/compose 2016-12-06 19:05:05 +00:00

README.md

Tests are divided into three groups:

  • Tests in the check directory are non-destructive and uninstalled. Some of the tests require root privileges. Use make check to run these.

  • The composecheck tests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.

    To use them, you might do a make && sudo make install inside a Docker container.

    Then invoke ./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.

    Note: This is intentionally not a Makefile target because it doesn't require building and doesn't use uninstalled binaries.

  • Tests in the vmcheck directory are oriented around using Vagrant. Use make vmcheck to run them. See also HACKING.md in the top directory.

The common directory contains files used by multiple tests. The utils directory contains helper utilities required to run the tests.