From b9f9291c62233de8020e2c67268de49cfcac789f Mon Sep 17 00:00:00 2001 From: Jelle van der Waa Date: Wed, 23 Aug 2023 10:25:00 +0200 Subject: [PATCH] Update test/ARCHITECTURE.md Co-authored-by: Martin Pitt --- test/ARCHITECTURE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/ARCHITECTURE.md b/test/ARCHITECTURE.md index 66d71c3522c7..2d41eda143c0 100644 --- a/test/ARCHITECTURE.md +++ b/test/ARCHITECTURE.md @@ -255,8 +255,8 @@ allow for faster retrying. The `test/run` prepares an Virtual machine image for the given `TEST_OS` and then runs the tests by calling `test/common/run-tests` with the provided tests. -For the Testing Farm (TF) scenario, Packit is responsible for setting up the -test infrastructure and the entry point is `test/browser/browser.sh`. On TF we +The [tmt](https://tmt.readthedocs.io) test is defined in [test/browser/main.fmf](./browser/main.fmf). These +run on the Testing Farm (TF), triggered by [Packit](https://packit.dev/) for upstream PRs. On TF we get a single virtual machine without a hypervisor so tests run on the virtual machine directly this also implies that only `destructive` tests can be run. The `test/browser/browser.sh` script sets up the virtual machine and calls