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-cache.sh | ||
build-dry.sh | ||
build-with-garbage-path.sh | ||
build.sh | ||
common.sh | ||
concurrent-builds.sh | ||
config.nix.in | ||
content-addressed.nix | ||
derivation-json.sh | ||
duplicate-realisation-in-closure.sh | ||
eval-store.sh | ||
flake.nix | ||
gc.sh | ||
import-derivation.sh | ||
local.mk | ||
meson.build | ||
new-build-cmd.sh | ||
nix-copy.sh | ||
nix-run.sh | ||
nix-shell.sh | ||
nondeterministic.nix | ||
post-hook.sh | ||
racy.nix | ||
recursive.sh | ||
repl.sh | ||
selfref-gc.sh | ||
signatures.sh | ||
substitute.sh | ||
why-depends.sh |