From 2f1d137717eeb487f4a26dbd3296fbbb3c0c7799 Mon Sep 17 00:00:00 2001 From: Badri Vishal Pandey Date: Tue, 27 Oct 2026 20:58:27 +0530 Subject: [PATCH] docs: describe testing an installed build --- testing/run-write-tests.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/testing/run-write-tests.rst b/testing/run-write-tests.rst index 405d10f039..6e6624da13 100644 --- a/testing/run-write-tests.rst +++ b/testing/run-write-tests.rst @@ -160,6 +160,18 @@ using several Python processes so as to speed up things: .\python.bat -m test -j0 +To check that the test suite is included in an installed build, install Python +to a fresh prefix and run the test suite with that installation. For example, +on Unix:: + + ./configure --prefix=/tmp/cpython-install + make -j3 + make install + /tmp/cpython-install/bin/python3 -m test -j3 + +Using the installed interpreter is important: running ``./python -m test`` from +the checkout tests the build tree, not the installed files. + .. _strenuous_testing: Finally, if you want to run tests under a more strenuous set of settings, you