From 08b2c872d66b7daaab4fc6698f6336dd59fd19b8 Mon Sep 17 00:00:00 2001
From: Martchus <martchus@gmx.net>
Date: Tue, 14 Nov 2023 01:52:12 +0100
Subject: [PATCH] Improve Plasmoid testing script and documentation

---
 plasmoid/scripts/settestenv.sh | 3 +++
 plasmoid/testing.md            | 5 ++++-
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/plasmoid/scripts/settestenv.sh b/plasmoid/scripts/settestenv.sh
index 436f0c6..b11e0b6 100755
--- a/plasmoid/scripts/settestenv.sh
+++ b/plasmoid/scripts/settestenv.sh
@@ -25,3 +25,6 @@ export TEST_FILE_PATH=$(dirname "${BASH_SOURCE[0]}")/../testfiles
 
 # log working directory
 echo "Working directory used for Plasmoid testing: $PWD"
+
+# debug plugin loading (run this script from terminal if Qt Creator suppresses the debugging output)
+export QT_DEBUG_PLUGINS=1
diff --git a/plasmoid/testing.md b/plasmoid/testing.md
index ef012d5..f80aa66 100644
--- a/plasmoid/testing.md
+++ b/plasmoid/testing.md
@@ -15,6 +15,8 @@ rather than the regular home to separate testing from production.
     looks like within the system tray plasmoid.
   * This usage of `%{sourceDir}` assumes one used the "Building this straight" instructions
     from the main README.md.
+  * When using a suffix (e.g. development build via CMake presets), this suffix needs to be appended
+    to the applet name.
 5. Keep `%{buildDir}` as working directory.
 6. In execution environment there's nothing mandatory to be set because `starttesting.sh` should
    already take care of setting the environment.
@@ -23,7 +25,8 @@ rather than the regular home to separate testing from production.
       set in accordance.
     * If not already set, `QT_PLUGIN_PATH` is set to `$CMAKE_CURRENT_BINARY_DIR/plasmoid/lib` which
       should contain the plugin for the Plasmoid under `plasma/applets/*syncthingplasmoid*.so`.
-    * Set `QT_DEBUG_PLUGINS` to 1 for verbose plugin detection.
+    * Set `QT_DEBUG_PLUGINS` to 1 for verbose plugin detection (the verbose output might be suppressed
+      when starting via Qt Creator so it may be worthwile to start this from a terminal).
 7. Ignore warning that executable is no debug build, it is sufficient when
    the plugin is a debug build (see next section for QML debugging).