rpm-ostree/tests
Jonathan Lebon 0da9f9972b tests/vmcheck: Adapt to kernel v5.0
Closes: #1810
Approved by: jlebon
2019-04-05 19:28:39 +00:00
..
check libpriv/kargs: Strengthen and simplify new kargs APIs 2019-03-23 18:48:05 +00:00
common tests/libtest.sh: Lift assert_jq from libvm.sh 2019-02-27 01:05:43 +00:00
compose-tests compose: Add --download-only-rpms 2019-03-25 14:33:17 +00:00
composedata ci: Bump to f29 2019-03-19 12:19:38 +00:00
ex-container-tests ci: Bump to f29 2019-03-19 12:19:38 +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 Print CVEs fixed in available updates 2018-12-05 18:56:49 +00:00
vmcheck tests/vmcheck: Adapt to kernel v5.0 2019-04-05 19:28:39 +00:00
compose compose: Add --download-only-rpms 2019-03-25 14:33:17 +00:00
ex-container ci: Fix ex-container LOGDIR 2019-03-19 12:19:38 +00:00
README.md tests: Add ./tests/compose 2016-12-06 19:05:05 +00:00

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.