agentleFS
MicrosoftKnown publishermicrosoft/fluentui-react-native/.github/skills/desktop-testing/SKILL.md

desktop-testing

Skill1.4k starsChanged 5 months agoMITView on GitHub

Configure, run, or troubleshoot native desktop tests using desktop-test, desktop-driver, and storybook-desktop, including app targets and suites, helpers, permissions, WDIO suites, Storybook story tests and smoke runs, reports, and CI. Not for package source changes or the Storybook app build toolchain.

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/fluentui-react-native repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about microsoft/fluentui-react-native

The biggest 5 of 37 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 37

Talked about on GitHub and Bluesky (37 times).

On GitHub · 36

31 more on GitHub

On Bluesky · 1

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not change privacy settings without authorization or overlap interactive desktop workloads.

    line 30
  2. Very specific:

    If a published package changed, add its changeset.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Desktop testing

Package references own commands, schemas, and troubleshooting. Read only the matching topic; do not copy its content here.

TaskRead
Add an app target or suitedesktop-test configuration
Run stages, suites, or inspect resultsdesktop-test commands and reporting
Prepare a platform or provision a helperdesktop-test platforms and desktop-driver helpers
Integrate Storybook or run callbacksstorybook-desktop integration, commands, and tests
Fix E2E adapters or diagnose failuresdesktop-test WDIO suites and lifecycle

For machine-readable output, use the package command references for shared --reporter modes; use NDJSON progress only when a live event stream is useful.

Workflow

  1. Identify the consumer workspace; read its config and declared scripts. For apps/storybook, also read AGENTS.md and agent-map.yaml.
  2. Reproduce with the narrowest declared stage, suite, story, or filter. Provision the verified helper explicitly; never guess flags or call runner internals.
  3. Do not change privacy settings without authorization or overlap interactive desktop workloads.
  4. Report failures, skips, unsupported capabilities, and incomplete work distinctly. Skips are not passes.
  5. If a published package changed, add its changeset. Finish code/config changes with yarn clean-lage-cache then yarn lage buildci.

For package source changes or reviews, use maintain-desktop-testing. For the apps/storybook build/toolchain, use agentic-storybook-development. Component story assertions stay with agentic-component-authoring; v0/v1 FluentTester assertions stay with maintain-v0-v1-component.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.