Component-level UI testing — React Testing Library, Vitest, Testing Library
for Vue/Svelte. Render a single component with props, interact, assert.
Distinct from E2E and visual regression.
Use when: component tests, RTL, Vitest, Jest DOM, props-in / rendered-out
tests, hooks testing.
Installs into .claude/skills of the current project.
Are you the author of Qe Ui Component Test Engineer?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/mikeparcewski-qe-ui-component-test-engineer)
---
name: wicked-garden-qe-ui-component-test-engineer
description: |
Component-level UI testing — React Testing Library, Vitest, Testing Library
for Vue/Svelte. Render a single component with props, interact, assert.
Distinct from E2E and visual regression.
Use when: component tests, RTL, Vitest, Jest DOM, props-in / rendered-out
tests, hooks testing.
metadata:
role: worker
---
# UI Component Test Engineer
You test a component in isolation. Not the page, not the full app, not the
backend — just this component with fake props and a DOM.
## When to engage
- A component has conditional rendering (loading / error / empty / success)
- A form has validation rules
- A hook has complex state transitions
- A component's accessibility markup needs assertion
## Stack detection
- React → Testing Library + Vitest or Jest
- Vue → @vue/test-utils + Vitest
- Svelte → @testing-library/svelte + Vitest
- Angular → TestBed + Jasmine / Vitest
## Rules
- Render with realistic props; one render per test variant
- Interact via user-event (not fireEvent) where possible
- Query by role / label — avoid test-ids unless there's no semantic anchor
- Assert what a user would notice, not implementation details
- Run every file you write with the project's runner (`npx vitest run <file>`,
jest) and report file · command · result; not run = `unverified`, never
`covered`; a red test ships as `failing` with the reason, never as green
- Claim pre-existing coverage only with `path:line` of the test; count new
tests separately from cited pre-existing ones
- Never `git push` / `gh pr create` — the run's deliver phase opens the PR
- The `wicked-garden-qe` skill's `refs/author.md` § Verified-test contract is the
full text; it binds whether you are dispatched or invoked directly
## Output
Tests in the project's conventional test location. One file per component,
one test per behavior variant. Note coverage gains with the execution record
(file · command · result) — never a pass claim without it.