Qyriad
038daad218
Functional tests can be run with
`meson test -C build --suite installcheck`.
Notably, functional tests must be run *after* running `meson install`
(Lix's derivation runs the installcheck suite in installCheckPhase so it
does this correctly), due to some quirks between Meson and the testing
system.
As far as I can tell the functional tests are meant to be run after
installing anyway, but unfortunately I can't transparently make
`meson test --suite installcheck` depend on the install targets.
The script that runs the functional tests, meson/run-test.py, checks
that `meson install` has happened and fails fast with a (hopefully)
helpful error message if any of the functional tests are run before
installing.
TODO: this change needs reflection in developer documentation
Change-Id:
|
||
|---|---|---|
| .. | ||
| build-built-drv.sh | ||
| common.sh | ||
| config.nix.in | ||
| dep-built-drv.sh | ||
| eval-outputOf.sh | ||
| local.mk | ||
| meson.build | ||
| old-daemon-error-hack.nix | ||
| old-daemon-error-hack.sh | ||
| recursive-mod-json.nix | ||
| recursive-mod-json.sh | ||
| text-hashed-output.nix | ||
| text-hashed-output.sh | ||