From 4a722d2e8e7b01c4c07a739b8305c3704644292c Mon Sep 17 00:00:00 2001 From: Thomas Huth Date: Tue, 12 Nov 2024 12:53:02 +0100 Subject: docs/devel/testing/functional: Clarify that we have to use the build folder Make it clear that the commands have to be run from the folder with the build, and use the python3 from our pyvenv to make sure that the pycotap module is available. Message-ID: <20241112115302.470527-1-thuth@redhat.com> Signed-off-by: Thomas Huth --- docs/devel/testing/functional.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs') diff --git a/docs/devel/testing/functional.rst b/docs/devel/testing/functional.rst index b8ad7b0bf7..ae238ed3fc 100644 --- a/docs/devel/testing/functional.rst +++ b/docs/devel/testing/functional.rst @@ -59,11 +59,12 @@ To run a single test file without the meson test runner, you can also execute the file directly by specifying two environment variables first, the PYTHONPATH that has to include the python folder and the tests/functional folder of the source tree, and QEMU_TEST_QEMU_BINARY that has to point -to the QEMU binary that should be used for the test, for example:: +to the QEMU binary that should be used for the test. The current working +directory should be your build folder. For example:: $ export PYTHONPATH=../python:../tests/functional $ export QEMU_TEST_QEMU_BINARY=$PWD/qemu-system-x86_64 - $ python3 ../tests/functional/test_file.py + $ pyvenv/bin/python3 ../tests/functional/test_file.py The test framework will automatically purge any scratch files created during the tests. If needing to debug a failed test, it is possible to keep these -- cgit v1.2.3