keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
fbdbddb3d4
rpm-ostree/tests
History
Colin Walters fbdbddb3d4 vmcheck: Support a VMCHECK_DEBUG to not reset the system 
I want to be able to debug a test by sshing in with the same setup;
right now the suite resets and reboots by default.

This also required fixing how we deal with `/etc/yum.repos.d`, since at the
start of the test it could be either pristine or not.

Closes: #578
Approved by: jlebon
2017-04-11 16:04:29 +00:00
..
check tests/ucontainer: Also disable xattrs here 2017-04-04 17:48:26 +00:00
common vmcheck: Support VMCHECK_INSTTREE 2017-03-27 17:48:39 +00:00
compose-tests compose: Delete /usr/etc/passwd- (and the other variants) 2017-03-20 16:35:17 +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 ci: Build ostree from git temporarily 2017-03-27 16:35:43 +00:00
vmcheck vmcheck: Support a VMCHECK_DEBUG to not reset the system 2017-04-11 16:04:29 +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.