[websites/linux-kde-org] content/docs: docs: update openQA documentation

Git commit dd2be835b91cae829c4a73dd342279e9d9ff311e by Bhushan Shah, on behalf of Bhushan Shah.
Committed on 25/07/2026 at 14:35.
Pushed by bshah into branch 'master'.

docs: update openQA documentation

- Add information about disk encryption test suite
- Add information about additional logs

M  +14   -2    content/docs/openqa.md

https://invent.kde.org/websites/linux-kde-org/-/commit/dd2be835b91cae829c4a73dd342279e9d9ff311e

diff --git a/content/docs/openqa.md b/content/docs/openqa.md
index a71df16..fe39ba4 100644
--- a/content/docs/openqa.md
+++ b/content/docs/openqa.md
@@ -37,7 +37,7 @@ The link provided after the log message *“In case of failure, you can inspect
 
 Open the job in the openQA web UI and select the failed module first. The link to the web UI will appear after the *“<name> test job is now running.”* log message. Its details include the module result, screenshots or video where applicable, and diagnostic output. In the *Logs & Assets* tab, download or view `autoinst-log.txt` for the openQA worker and test-engine log. This is the primary log for the job itself.
 
-For tests that execute commands on the system under test, KDE Linux runs them in transient systemd services and records the service journal as diagnostic output in the test result. Inspect `autoinst-log.txt` for the command output and journal.
+For tests that execute commands on the system under test, KDE Linux runs them in transient systemd services and records the service journal as diagnostic output in the test result. Inspect `autoinst-log.txt` for the command output and journal. You can also download the <code>*kde-linux-collected-logs.tar.zst</code> file for logs captured by the <code>collect-logs</code> tool.
 
 ## Run tests locally
 
@@ -60,12 +60,24 @@ podman exec -it openqa-single-instance bash
 bash utils/jobs.sh
 </pre>
 
-To run the upgrade flow instead, add <code>--upgrade</code>.
+To run the upgrade flow instead, add <code>--upgrade</code>:
 
 <pre>
 bash utils/jobs.sh --upgrade
 </pre>
 
+To run the disk-encryption install-test flow, add <code>--encrypt</code>:
+
+<pre>
+bash utils/jobs.sh --encrypt
+</pre>
+
+You can also combine <code>--upgrade</code> and <code>--encrypt</code> options:
+
+<pre>
+bash utils/jobs.sh --upgrade --encrypt
+</pre>
+
 The `sanity-test` job needs the `install-system` job to run first because it uses the virtual disk created by the installation. To concentrate on a particular test, adjust the submitted jobs in <code>utils/jobs.sh</code> while keeping that dependency in mind.
 
 When you are finished, stop the stack and remove its local volumes.