Skip to content
Agentmart
Submit a tool

component-testing

Test meaningful frontend component behavior through user-visible state, input, events, and accessibility semantics.

Skill by yousofdavamkar

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/yousofdavamkar-component-testing

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Test meaningful frontend component behavior through user-visible state, input, events, and accessibility semantics. Use for interactive React components, forms, overlays, and stateful UI.

Use cases: design, frontend, testing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/component-testing

What's inside

Skill name
component-testing
Description
Test meaningful frontend component behavior through user-visible state, input, events, and accessibility semantics. Use for interactive React components, forms, overlays, and stateful UI.
License
MIT
Instructions
9 lines in SKILL.md · view on GitHub

Files (3)

  • SKILL.md
  • openai.yaml · agents/
  • frontier.skill.yaml

SKILL.md (first lines)

# Component Testing

Render the component through its public API and interact as a user would. Query by role, accessible name, label, or visible content. Verify the initial state, meaningful transition, result, and applicable failure or disabled state.

Mock only external boundaries that cannot be exercised deterministically. Do not assert hook calls, internal state, implementation-specific class names, or markup that has no behavioral contract.

Keep each test focused on one outcome while sharing setup only when it remains clear.

From yousofdavamkar/frontier, MIT.

More from yousofdavamkar/frontier

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Aug 1, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from yousofdavamkar

Cite this page

component-testing skill. Agent Mart. https://agentmart.dev/skills/yousofdavamkar-component-testing (last updated 2026-10-24)