b54b8744b9
We would error out when trying to start the transient httpd service if it already exists, e.g. from a previous test. Depending on how we exit, the `vm_stop_httpd` trap for the previous test might not have been able to kick in. I think this happens when we exit using `fatal`, which just does an `exit 1`. It's not strictly an error, so doesn't trip the `ERR` handler. Let's just go the extra mile and explicitly delete transient services if they already exist. Closes: #1284 Approved by: cgwalters |
||
---|---|---|
.. | ||
check | ||
common | ||
compose-tests | ||
composedata | ||
ex-container-tests | ||
gpghome | ||
manual | ||
utils | ||
vmcheck | ||
compose | ||
ex-container | ||
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. Usemake 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. Usemake vmcheck
to run them. See alsoHACKING.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.