javascript-testing-patterns

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with executable examples and a clean one-level reference structure, but the body is long and inlines reference-grade material that overlaps the bundle, with no sequenced workflow or validation checkpoints.

Suggestions

Move the duplicate/extended inline patterns (e.g., the second UserService DI example, full async and mocking pattern sets) into references/advanced-testing-patterns.md and keep only one representative example per category inline, to reduce token overlap.

Add a short sequenced workflow with checkpoints for the genuinely procedural tasks (e.g., 'set up framework -> write failing test -> implement -> run coverage -> verify 80% threshold') rather than only a flat Best Practices list.

Include at least one inline E2E example or a concrete pointer section, since end-to-end testing is named in the description but has no executable example in the body.

Dimension	Reasoning	Score
Conciseness	Prose is lean and avoids explaining concepts Claude already knows, but ~537 lines inlines large reference-grade code blocks (e.g., two distinct UserService examples, full pattern sets that overlap the bundle) that could be tightened or split out.	3 / 5
Actionability	Fully executable, copy-paste-ready TypeScript test files, framework configs, mocking/spying examples, and a faker fixture factory covering the common cases.	5 / 5
Workflow Clarity	Organized as a topical pattern catalog with a sensible progression and a best-practices list, but it is not a multi-step workflow and contains no validation checkpoints or feedback loops.	3 / 5
Progressive Disclosure	A single one-level-deep, well-signaled reference file (references/advanced-testing-patterns.md, no nested refs) is linked three times with clear topical labels, though some content is duplicated inline rather than cleanly split.	4 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities with named frameworks and concrete trigger phrases for both what and when. Only minor gap is the breadth of casual synonyms/extensions in trigger terms.

Dimension	Reasoning	Score
Specificity	Names specific frameworks (Jest, Vitest, Testing Library) and multiple concrete actions across unit, integration, and end-to-end testing plus mocking, fixtures, and TDD — comprehensive coverage matching the 5 anchor.	5 / 5
Completeness	Explicitly answers both what (comprehensive testing strategies with named frameworks and test types) and when ('Use when writing JavaScript/TypeScript tests...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('writing JavaScript/TypeScript tests', 'setting up test infrastructure', 'TDD/BDD workflows') with synonyms, but missing the full extension/casual-synonym spread of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Framework-specific JS/TS testing niche with explicit triggers gives a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (538 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/javascript-typescript/skills/javascript-testing-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.