qa-desktop

Action-taking agent that reads a target Windows / macOS / Linux / cross-platform desktop project (`*.csproj` / `*.sln` / `package.json` / `*.pro` / `CMakeLists.txt`) and emits one concrete desktop UI driver recommendation - FlaUI, WinAppDriver, Appium-Windows, electron-playwright, QtTest, XCUITest, or AT-SPI - plus rationale and which preloaded SKILL.md to read next. Distinct from `qa-process/framework-choice-advisor` (pure-reference catalog of e2e/load frameworks laying out trade-offs in prose): this agent reads the actual target repo and returns one desktop UI driver per app rather than enumerating options. Use when starting a new desktop test project and the team has not yet committed to a driver.

Action-taking agent that, given a user-flow spec + a target desktop app + a chosen driver, authors one desktop UI test file plus any new screen-object additions. Composes the eight qa-desktop driver skills (Windows: flaui-tests, winappdriver, appium-windows-driver; Electron: electron-playwright, electron-spectron; Qt: qt-test-framework; macOS: xctest-mac-desktop; Linux: at-spi-linux) plus desktop-test-strategy-reference, with the .NET xunit-tests / nunit-tests / mstest-tests harness skills from `qa-unit-tests-net`. Distinct from `qa-shift-left/spec-to-suite-orchestrator` (language-agnostic, multi-stage workflow producing a project skeleton): narrower platform (desktop only); output is one test file per spec; defers driver + framework choice to upstream selector agents. Use when adding a new per-flow desktop test to an existing test project.

Adversarial read-only reviewer for desktop UI test files (WPF, WinForms, Electron, Qt, macOS Cocoa/SwiftUI). Inspects each test for screen-object encapsulation, locator-stability (AutomationId over Name/index per [Microsoft Learn][msautoid]), explicit-wait primitives over raw sleep, and desktop-specific hazards (STA threading, foreground-window lock, OS elevation). Emits a per-file findings table and a BLOCK or PASS verdict. Distinct from `test-code-critic` (§1-§10 file conventions, framework-agnostic) and `e2e-selector-quality-critic` (web DOM selectors only) - this agent is desktop-platform-specific. Use when reviewing an existing desktop UI test suite or a PR that touches desktop test files.

Builder agent that emits a fresh desktop UI test project - test project file (`.csproj` or `package.json`), driver-init module, one placeholder screen-object / page-object class with explicit selector-confirmation markers, and a CI workflow stub tagged for the matching Windows / macOS / Linux runner. Distinct from `qa-web-e2e/spec-to-e2e-test-scaffolder` (Playwright / Cypress / Selenium / WebdriverIO fixture-shaped scaffolds): this scaffolds for desktop drivers (FlaUI / WinAppDriver / Appium-Windows / electron-playwright / QtTest / XCUITest / AT-SPI) and emits driver-init + screen-object skeletons rather than browser fixtures. Use when starting a brand-new desktop test project after `desktop-driver-selector` has picked the driver.

Authors and runs Qt Test - the first-party C++ unit + GUI test framework that ships with Qt 6 (`#include <QtTest>`). Covers the `QTEST_MAIN` / `QTEST_APPLESS_MAIN` / `QTEST_GUILESS_MAIN` entry-point macros, the `QObject` private-slot test pattern, `QVERIFY` / `QCOMPARE` / `QFETCH` assertions, GUI event simulation (`QTest::mouseClick`, `QTest::keyClick`, `QTest::touchEvent`), `QSignalSpy` for signal introspection, `QBENCHMARK` for performance regression, and the `-o file,junitxml` CI output. Use for in-process testing of Qt widgets, QObject signal/slot chains, and Qt Quick / QML application logic; for out-of-process Qt-app driving see the OS drivers in this plugin.

Authors and runs Windows UI tests against WinAppDriver - Microsoft's W3C-WebDriver service for UWP, WPF, WinForms, and Win32 applications. Covers installing + launching `WinAppDriver.exe` on the default `127.0.0.1:4723` endpoint, declaring `app` / `platformName` / `appArguments` / `appTopLevelWindow` capabilities, finding elements by `AccessibilityId` / `Name` / `ClassName`, and CI integration on Windows runners. Use when driving a native Windows desktop app from a Selenium-style client (C#, Java, Python, Ruby, JavaScript).

Authors and runs XCTest UI + unit tests for macOS desktop apps - the Apple-first-party test framework that ships with Xcode. Covers the `XCTestCase` subclass + `test*` method-naming convention, `XCUIApplication` / `XCUIElement` / `XCUIElementQuery` for UI tests, accessibility-identifier-based locators (the stable replacement for label-based queries), `XCTAssert*` macros, `measureBlock:` for performance regressions, and `xcodebuild test` for CI execution. Use when the macOS app is built with Xcode and the test target is in-tree alongside the app - for cross-OS sharing see Appium Mac2 driver as a separate path.

Legacy reference for Spectron - Electron's original ChromeDriver-based testing framework, officially deprecated 2022-02-01 at v19.0.0. Documents what Spectron was, the architectural reason it became unmaintainable, the migration path to Playwright `_electron`, and the residual support contract for projects still on Spectron. Use only when auditing a legacy suite or planning a migration off Spectron - for new work use `electron-playwright` in this plugin.

Authors and runs FlaUI-based Windows UI tests - the .NET-native wrapper around Microsoft UI Automation (UIA2 + UIA3). Covers the `FlaUI.Core` / `FlaUI.UIA2` / `FlaUI.UIA3` NuGet packages, `Application.Launch` / `Application.Attach` lifecycles, `ConditionFactory` + `FindFirstDescendant` locator patterns, `Retry` waits, and xUnit / NUnit / MSTest harness integration. Use when the test stack is C# / .NET-first and the team wants idiomatic in-process UIA calls rather than the HTTP/JSON wire protocol of `winappdriver` or the Appium proxy layer of `appium-windows-driver`.