keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
127275fe0e
rpm-ostree/tests
History
Colin Walters 22048b25a7 scripts: Use tmpfs for /var/tmp, not the host's /tmp 
We don't want to expose the host's `/tmp` since that means scripts could
potentially find things like the X11 socket or whatever.

To debug things better, add a quick bash script to run bwrap like the C code
does. Perhaps down the line we can add `rpm-ostree internals run-bwrap` or so.

Closes: #647
Approved by: jlebon
2017-02-28 23:37:15 +00:00
..
check daemon: Implement "reload" 2017-02-24 21:36:45 +00:00
common scripts: Use tmpfs for /var/tmp, not the host's /tmp 2017-02-28 23:37:15 +00:00
compose-tests compose-tests: add more mutate-os-release cases 2017-02-01 22:25:54 +00:00
composedata compose: fix bad baseurl 2017-01-21 15:27:11 +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 start-daemon: make hidden 2017-02-10 20:11:27 +00:00
vmcheck scripts: Use tmpfs for /var/tmp, not the host's /tmp 2017-02-28 23:37:15 +00:00
compose core: add RPMOSTREE_USE_CACHED_METADATA 2017-01-08 21:05:06 +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.