Integrate the system test runner to work with meson build system. On each compilation, create build-dependent variables in isctest/vars/.build_env. Then, run a custom script (on every single rebuild) to put TOP_BUILDDIR into the source directory (as well as ifconfig.sh for developer convenience). When pytest is executed, it always reads TOP_BUILDDIR variable from the source directory where it was placed by the previously. Then it knows which directory to use to read the remaining build variables and proceeds as usual. meson test command was considered for running system tests, but ultimately it seems that running pytest directly (from source dir as devs are used to) is a better solution. Some of the issues with meson test include: different test granularity from `pytest`, having to maintain extra list of tests, incorrect reporting of skipped tests, no advance usage (e.g. using pytest's options) and maintaining two slightly different ways of running system tests.
2 lines
11 B
Plaintext
2 lines
11 B
Plaintext
@XSLTPROC@
|