keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c039b72ebd
rpm-ostree/tests
History
Colin Walters c039b72ebd importer: Use /run instead of /var/run 
Translate RPM paths under `/var/run` to `/run` automatically; this
quiets down systemd.  Since we end up running `systemd-tmpfiles`
a few times in FCOS reducing spew here is particularly valuable.

The bug is really in the packages here but...we don't have an
agile process for fixing them.

Note that for this fix to take effect, if you have a `cache/pkgcache-repo`
you'll need to remove it.
2020-02-03 07:50:10 -08:00
..
check compose: Add an automatic-version-suffix key 2019-12-13 17:11:16 +01:00
common tests/compose: Target FCOS 31, move off of PAPR 2020-01-08 16:42:54 +01:00
compose importer: Use /run instead of /var/run 2020-02-03 07:50:10 -08: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 tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
utils tests: Add hidden testutils subcommand 2019-12-13 19:18:30 +01:00
vmcheck libpriv/util: Fix human diff printing for upgrades/downgrades 2020-01-21 18:36:53 +01:00
compose.sh tests/compose: Target FCOS 31, move off of PAPR 2020-01-08 16:42:54 +01: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
vmcheck.sh tests/compose: Target FCOS 31, move off of PAPR 2020-01-08 16:42:54 +01: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.