CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/desktop-test-strategy-reference

Reference catalog of desktop GUI test strategies across Windows, macOS, and Linux. Defines the three accessibility-tree backends (Microsoft UI Automation on Windows, Apple Accessibility / XCTest on macOS, AT-SPI on Linux), the wrapper-tools that drive each backend, the cross-toolkit Electron + Qt paths, the project-marker detection table plus one-driver-per-app decision table (FlaUI / WinAppDriver / electron-playwright / QtTest / XCUITest / AT-SPI), an accessibility-first locator strategy, and a desktop test-review hazard checklist (screen-object encapsulation, locator stability, explicit waits, STA / foreground-lock / elevation). Deep operational detail (per-OS async-wait hierarchies, parallel-test policy, UAC / TCC / AT-SPI elevation hazards, the high-DPI matrix) lives in references/. Use when choosing how to test or automate a desktop GUI application on Windows, macOS, or Linux, or when reviewing an existing desktop UI test suite - the strategic reference ahead of the per-tool implementation skills.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured strategic reference with strong progressive disclosure — a lean overview pointing to two real one-level-deep reference files — and concrete, specific decision guidance throughout. The main gaps are minor verbosity in quoted doc excerpts and the absence of runnable code, appropriate for a reference skill but leaving actionability just short of exemplary.

Suggestions

Trim or paraphrase the verbatim Microsoft/Apple/at-spi blockquotes to the operative sentence to recover tokens without losing citation value.

Where the locator-strategy and decision tables reference driver APIs, add a one-line minimal example (e.g. a `Retry.WhileNull` or `waitForExistence(timeout:)` snippet) to lift actionability toward copy-paste-ready.

Consider promoting the two reference-file links into the 'How to use this reference' list itself so the entry-point workflow surfaces both deep references up front.

DimensionReasoningScore

Conciseness

Mostly dense, high-signal tables and decision matrices that assume Claude's competence; minor over-explanation in verbatim doc quotes and restated backend framing that could be trimmed.

4 / 5

Actionability

Highly actionable decision tables and exact API/pattern names (AutomationId, accessibilityIdentifier, <UseWPF>true</UseWPF>, find_package(Qt6)), but as a strategic reference it offers selection guidance and pointers rather than copy-paste runnable code blocks.

4 / 5

Workflow Clarity

Clear numbered 'How to use this reference' sequence and a two-stage driver-selection workflow with explicit constraints and hard-reject rules; advisory checkpoints rather than full validate→fix→retry loops, fitting a reference/decision skill.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to two verified real files (async-waits-and-concurrency.md, platform-hazards-and-dpi.md), appropriately splitting strategic content inline from operational depth in references, with easy navigation and cross-links to per-tool skills.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, highly specific description that clearly states both what the skill provides and when to use it, with named tools and concrete triggers. It loses only a point on trigger-term breadth for missing a few common synonyms (QA, UI automation).

Suggestions

Add common trigger synonyms like 'QA' or 'UI automation' alongside 'test or automate' to broaden natural-keyword coverage.

Consider naming the OS backends (UIA / XCTest / AT-SPI) in the trigger clause so users phrasing by backend name land on this skill.

DimensionReasoningScore

Specificity

Names multiple concrete artifacts comprehensively — the three accessibility-tree backends, per-tool decision table (FlaUI/WinAppDriver/electron-playwright/QtTest/XCUITest/AT-SPI), locator strategy, and review hazard checklist — each with specific named tools.

5 / 5

Completeness

Explicitly answers both 'what' (reference catalog defining backends, decision table, locator strategy, hazard checklist) and 'when' ('Use when choosing how to test or automate... or when reviewing an existing desktop UI test suite') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('test or automate a desktop GUI application', 'reviewing an existing desktop UI test suite') with test/automate/review synonyms, but omits common variations like 'QA', 'UI automation', or per-OS terms as triggers.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — desktop GUI test strategy across Windows/macOS/Linux with named backends and drivers — and self-positions as 'the strategic reference ahead of the per-tool implementation skills', minimizing overlap risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 6 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents