qa-desktop
Desktop application testing for Windows (FlaUI, WinAppDriver), Electron (Playwright) and Qt (Qt Test), with a driver decision table. Also covers Linux AT-SPI, Spectron migration, and a test-review hazard checklist. An authoring agent (desktop-test-author) detects the driver, scaffolds a test project when none exists, and writes per-flow tests. macOS XCTest UI tests live in qa-mobile.
/plugin install qa-desktop@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Functional testing
- Version
v1.3.4- Contents
- 5 skills · 1 agent
- Part of
- qa-role-mobile-desktop
Skills5
desktop-test-strategy-referenceUse when choosing how to test or automate a desktop GUI app on Windows, macOS or Linux, or reviewing a desktop UI suite.skillelectron-playwrightUse whenever an Electron desktop app needs end-to-end tests, or a Spectron suite must be migrated: Playwright's _electron.launch, renderer windows as Pages, main-process checks via electronApp.evaluate, and IPC and DOM assertions from one suite.skillflaui-testsUse when a Windows desktop app needs UI tests from C# or .NET with in-process UI Automation calls: FlaUI UIA2 and UIA3 packages, launching or attaching to the app, ConditionFactory locators, Retry waits and xUnit, NUnit or MSTest.skillqt-test-frameworkUse whenever Qt C++ code needs unit or GUI tests in-process: Qt Test entry macros, private-slot test functions, QVERIFY, QCOMPARE and data-driven QFETCH, simulated mouse, key and touch events, QSignalSpy, QBENCHMARK and JUnit XML output for CI, including Qt Quick and QML logic.skillwinappdriverUse when a native Windows app (UWP, WPF, WinForms, Win32) must be driven from a Selenium-style client in C#, Java, Python, Ruby or JS: WinAppDriver directly or through the Appium 2 Windows driver, capabilities, AccessibilityId and Name locators, and Windows CI runners.skill
Agents1
About qa-desktop
Desktop application testing across Windows (FlaUI, WinAppDriver - direct or Appium-invoked), macOS (XCTest UI via qa-mobile's xcuitest-suite), Linux (AT-SPI), Electron (Playwright _electron API, incl. Spectron migration), and Qt (QtTest framework). The desktop-test-author agent detects the driver, scaffolds a fresh test project when none exists, and authors per-flow tests.
Choosing a driver for a concrete app - project-marker detection plus the one-driver-per-app decision table - lives in desktop-test-strategy-reference, alongside the desktop test-review hazard checklist.