keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
75f415f09f
rpm-ostree/tests
History
Jonathan Lebon 75f415f09f tests/libtest.sh: Lift assert_jq from libvm.sh 
We already had this logic, but it was in `libvm.sh`. Prep for using it
elsewhere.

Closes: #1766
Approved by: cgwalters
2019-02-27 01:05:43 +00:00
..
check libpriv/util: Add date field in auto-versioning 2019-01-14 18:49:41 +00:00
common tests/libtest.sh: Lift assert_jq from libvm.sh 2019-02-27 01:05:43 +00:00
compose-tests postprocess: Add /home -> /var/home SELinux substitution 2019-02-14 17:24:09 +00:00
composedata compose: Support not specifying a ref 2018-10-09 19:47:25 +00:00
ex-container-tests Lower initial SELinux policy load from compose to core 2018-10-23 13:40:46 +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: Don't make system user with differently-named group 2019-02-25 14:21:28 +00:00
compose tests: Rename one libcomposetest.sh 2018-09-10 17:06:10 +00:00
ex-container tests: Rename one libcomposetest.sh 2018-09-10 17:06:10 +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.