CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/desktop-test-strategy-reference

Pure-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 (WinAppDriver, Appium-Windows, XCUIApplication, AT-SPI clients), the cross-toolkit Electron + Qt paths, and a per-OS decision matrix with accessibility-first locator strategy. Deep operational detail (per-OS asynchronous-wait hierarchies, parallel-test policy, foreground-lock / UAC / TCC / AT-SPI elevation hazards, and the high-DPI / per-monitor test matrix) lives in references/. Use as the strategic reference before picking a desktop test stack, ahead of the per-tool implementation skills.

74

Quality

93%

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

85%

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 actionability, clear sequenced usage workflow, and exemplary progressive disclosure into two real companion references. The only weakness is conciseness: some quoted external prose and explanatory passages run longer than a lean skill body requires.

Suggestions

Trim or paraphrase the blockquoted external-doc prose (e.g., the Microsoft UIA 'designed for experienced C/C++ developers' quote and the Apple XCTest quotes) to only the clause that justifies a claim, since the citations already carry provenance.

Compress the 'Localisation rule of thumb' paragraph — its point is already captured by the locator-strategy table's brittle-locator column and could be a one-line callout.

Consider collapsing the two 'Operating the tests - deep references' and 'References' sections, which currently re-list the same two reference links, to remove repetition.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with tables/citations rather than padding, but the ~300-line body includes several blockquoted prose passages from external docs (e.g., 'UI Automation is designed for experienced C/C++ developers...') that restate background and could be tightened; the localisation rule-of-thumb and some quoted material are longer than strictly needed.

2 / 3

Actionability

Provides concrete, executable guidance throughout: a per-OS/per-toolkit decision matrix, a locator-strategy table with specific identifiers (AutomationId, accessibilityIdentifier, setObjectName), named classes (XCUIApplication, XCUIElementQuery), and the references carry copy-paste commands (tccutil reset..., gsettings set org.gnome.desktop.interface toolkit-accessibility true).

3 / 3

Workflow Clarity

'How to use this reference' gives a clearly sequenced 4-step workflow (pick OS+toolkit, choose locators, apply async-wait primitive, pre-handle elevation hazard) with explicit ordering and a preventative checkpoint ('before it blocks the run'); the anti-pattern table pairs each failure with a concrete fix, providing recovery guidance.

3 / 3

Progressive Disclosure

SKILL.md is a well-organized overview that pushes deep operational detail into two clearly signaled, one-level-deep references — references/async-waits-and-concurrency.md and references/platform-hazards-and-dpi.md — both of which exist as real bundle files and are linked with descriptive context.

3 / 3

Total

11

/

12

Passed

Description

100%

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 highly specific, third-person description that clearly states both capabilities and explicit use-when triggers with natural user phrasing. It carves out a distinct strategic-reference niche that avoids conflict with the per-tool skills it points to.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and artifacts: 'Defines the three accessibility-tree backends', 'the wrapper-tools that drive each backend (WinAppDriver, Appium-Windows, XCUIApplication, AT-SPI clients)', 'cross-toolkit Electron + Qt paths', and 'a per-OS decision matrix with accessibility-first locator strategy'.

3 / 3

Completeness

Explicitly answers both: what it does ('Pure-reference catalog of desktop GUI test strategies...') and when to use it ('Use when choosing how to test or automate a desktop GUI application...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural user-facing terms in parentheses — 'desktop app testing, GUI automation, automate desktop UI' — matching the phrasing a user would actually say, alongside the domain vocabulary.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche ('the strategic reference before picking a desktop test stack, ahead of the per-tool implementation skills') that disambiguates it from sibling per-tool skills; triggers are specific to desktop GUI testing and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents