diff options
| author | Qyriad <qyriad@qyriad.me> | 2024-03-25 12:12:56 -0600 |
|---|---|---|
| committer | Qyriad <qyriad@qyriad.me> | 2024-03-27 18:37:50 -0600 |
| commit | 038daad2182a22c81861ee7cbb5f0c85f6bb16ba (patch) | |
| tree | 653f303e26bd99106a4d39d5cb9f880d4ba0a0a3 /tests/functional/common/meson.build | |
| parent | edba570664b952facde43fd0414e60f0a42851da (diff) | |
meson: implement functional tests
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: I8dcb5fdfc0b6cb17580973d24ad930abd57018f6
Diffstat (limited to 'tests/functional/common/meson.build')
| -rw-r--r-- | tests/functional/common/meson.build | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/tests/functional/common/meson.build b/tests/functional/common/meson.build new file mode 100644 index 000000000..74a8986e9 --- /dev/null +++ b/tests/functional/common/meson.build @@ -0,0 +1,6 @@ +# test_confdata set from tests/functional/meson.build +vars_and_functions = configure_file( + input : 'vars-and-functions.sh.in', + output : 'vars-and-functions.sh', + configuration : test_confdata, +) |