keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
d829311a3a
rpm-ostree/tests
History
Jonathan Lebon 4d845952c8 tests/compose: Add RPMOSTREE_TMPDIR_LOCATION 
This allows one to run the tests from a container using overlay +
SELinux protection by running the actual compose into a non-overlay
bind-mount. Otherwise, we'll hit `ENOTSUP` when trying to set labels on
various checkouts.

Closes: #1829
Approved by: cgwalters
2019-05-09 02:10:27 +00:00
..
check tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
common Copy used command-line and set as transaction title 2019-05-08 21:09:08 +00:00
compose-tests tests/compose: Add RPMOSTREE_TMPDIR_LOCATION 2019-05-09 02:10:27 +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 tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
utils tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
vmcheck Copy used command-line and set as transaction title 2019-05-08 21:09:08 +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

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.