@@ -38,14 +38,14 @@ directory (`OutputDirectory=`) to point to the other directory using `mkosi/mkos
3838After the image has been built, the integration tests can be run with:
3939
4040``` shell
41- $ env SYSTEMD_INTEGRATION_TESTS=1 mkosi -f sandbox -- meson test -C build --suite integration-tests --num-processes " $(( $(nproc) / 4 )) "
41+ $ mkosi -f sandbox -- meson test -C build --setup=integration --suite integration-tests --num-processes " $(( $(nproc) / 4 )) "
4242```
4343
4444As usual, specific tests can be run in meson by appending the name of the test
4545which is usually the name of the directory e.g.
4646
4747``` shell
48- $ env SYSTEMD_INTEGRATION_TESTS=1 mkosi -f sandbox -- meson test -C build -v TEST-01-BASIC
48+ $ mkosi -f sandbox -- meson test -C build --setup=integration -v TEST-01-BASIC
4949```
5050
5151See ` mkosi -f sandbox -- meson introspect build --tests ` for a list of tests.
@@ -55,7 +55,7 @@ To interactively debug a failing integration test, the `--interactive` option
5555newer:
5656
5757``` shell
58- $ env SYSTEMD_INTEGRATION_TESTS=1 mkosi -f sandbox -- meson test -C build -i TEST-01-BASIC
58+ $ mkosi -f sandbox -- meson test -C build --setup=integration -i TEST-01-BASIC
5959```
6060
6161Due to limitations in meson, the integration tests do not yet depend on the
@@ -64,7 +64,7 @@ running the integration tests. To rebuild the image and rerun a test, the
6464following command can be used:
6565
6666``` shell
67- $ mkosi -f sandbox -- meson compile -C build mkosi && env SYSTEMD_INTEGRATION_TESTS=1 mkosi -f sandbox -- meson test -C build -v TEST-01-BASIC
67+ $ mkosi -f sandbox -- meson compile -C build mkosi && mkosi -f sandbox -- meson test -C build --setup=integration -v TEST-01-BASIC
6868```
6969
7070The integration tests use the same mkosi configuration that's used when you run
@@ -78,7 +78,7 @@ To iterate on an integration test, let's first get a shell in the integration te
7878the following:
7979
8080``` shell
81- $ mkosi -f sandbox -- meson compile -C build mkosi && env SYSTEMD_INTEGRATION_TESTS=1 TEST_SHELL=1 mkosi -f sandbox -- meson test -C build -i TEST-01-BASIC
81+ $ mkosi -f sandbox -- meson compile -C build mkosi && mkosi -f sandbox -- meson test -C build --setup=shell -i TEST-01-BASIC
8282```
8383
8484This will get us a shell in the integration test environment after booting the machine without running the
@@ -107,7 +107,7 @@ re-running the test will first install the new packages we just built, make a ne
107107the test again. You can keep running the loop of ` mkosi -R ` , ` systemctl soft-reboot ` and
108108` systemctl start ... ` until the changes to the integration test are working.
109109
110- If you're debugging a failing integration test (running ` meson test --interactive ` without ` TEST_SHELL ` ),
110+ If you're debugging a failing integration test (running ` meson test --interactive ` ),
111111there's no need to run ` systemctl start ... ` , running ` systemctl soft-reboot ` on its own is sufficient to
112112rerun the test.
113113
@@ -120,10 +120,6 @@ rerun the test.
120120` TEST_NO_KVM=1 ` : Disable qemu KVM auto-detection (may be necessary when you're
121121trying to run the * vanilla* qemu and have both qemu and qemu-kvm installed)
122122
123- ` TEST_SHELL=1 ` : Configure the machine to be more * user-friendly* for
124- interactive debugging (e.g. by setting a usable default terminal, suppressing
125- the shutdown after the test, etc.).
126-
127123` TEST_MATCH_SUBTEST=subtest ` : If the test makes use of ` run_subtests ` use this
128124variable to provide a POSIX extended regex to run only subtests matching the
129125expression.
0 commit comments