agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/lit-webview-testing/SKILL.md

lit-webview-testing

Skill1k starsChanged 25 days agoBSD-3-ClauseView on GitHub

Write or review browser component tests for Lit webviews and VSCode Elements. Use for Playwright component harnesses, fake Effect services, accessibility locators, shadow DOM boundaries, lifecycle tests, and deciding what belongs in component tests versus VS Code E2E.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

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

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    No emulated acquireVsCodeApi() or local server.

    line 14

≈ “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

Lit webview browser testing

Real browser required for Lit updates, custom elements, popovers, shadow DOM, accessibility trees, and ElementInternals.

Harness boundary

  • Real Lit components, controller, and Effect application lifecycle; only extension backend replaced with a fake service layer.
  • No emulated acquireVsCodeApi() or local server.
  • Fake types derived from their factory/service source of truth—not handwritten copies.
  • Fakes support deterministic state emission, action recording, typed stream/dispatch failures, controllable latency, and resource counters.
  • Fake latency via Effect Clock; TestClock in Effect tests, not wall-clock waits.

What to test here

  • Component contracts and state/action flows: initial, loading, disabled, empty/no-match, invalid/recoverable, restored, external update, success, failure.
  • Action count/payload, including rapid or latent actions when cancellation/serialization matters.
  • Connect, disconnect, reconnect, listener/subscription cleanup, scoped finalization.
  • Keyboard, focus, theme, and form behavior where browser semantics matter.
  • Thin extension-host E2E: VS Code wiring, packaging, CSP/resources, desktop/web integration, critical journeys.

Interaction rules

  • Controls located by accessible role/name/label; documented public value/checked set before dispatching the public event.
  • Observable UI/application assertions—not private state or arbitrary render delays. Mount helper may await updateComplete to establish readiness.
  • Unavoidable shadow traversal isolated in 1 named helper, only for otherwise unobservable contracts such as ElementInternals form association.
  • Wrapper adapting an inaccessible nested node: user-visible accessibility assertion first; narrowly scoped implementation assertion only if needed.

Repository integration

  • Compile, fixture bundle, and browser execution in the package Wireit graph and relevant CI test:web path.
  • Package compile, lint, unit tests, and focused browser suite run from repository root.
  • General syntax/reliability: playwright-e2e. This skill owns the component-test boundary.

Examples: packages/soql-builder-ui/test/browser/, packages/soql-builder-ui/src/testing/fakeEffectService.ts.

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.

Check your setup, free