test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
73
1.06x
Quality
77%
Does it follow best practices?
Impact
99%
1.06x2 of 3 eval scenarios. Add 1 more for a full score.
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./dev-skills/skills/test-implement/SKILL.mdThe canonical home for this skill is test-implement in shinpr/claude-code-workflows
Test Implementation Patterns
Reference Selection
| Test Type | Reference | When to Use |
|---|---|---|
| Unit / Integration | references/frontend.md | Implementing React component tests with the repository's configured runner and network mocking layer |
| E2E | references/e2e.md | Implementing browser-level E2E tests in the existing harness, or Playwright when the approved work introduces a harness |
Common Principles
AAA Structure
All tests follow Arrange-Act-Assert:
- Arrange: Set up preconditions and inputs
- Act: Execute the behavior under test
- Assert: Verify the expected outcome
Test Independence
- Each test runs independently without depending on other tests
- No shared mutable state between tests
- Deterministic execution — mock random and time dependencies
Naming
- Test names describe expected behavior from user perspective
- One test verifies one behavior
- Repository
- shinpr/claude-code-workflows
- Commit
a4ecd62
- Last updated
- First committed
Canonical home
shinpr/claude-code-workflows
In sync
since Mar 27, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.