testing | experimental | ClaudePluginHub

Skill

Community

testing

From experimental

3

Description

Validates test coverage and quality by checking behavior focus, identifying gaps, and ensuring >80% statement coverage. Use when task file is in testing/ directory and requires test validation before marking complete. Adds minimal tests for genuinely missing edge cases.

Install

1

Add the repository(one-time)

$

/plugin marketplace add dhruvbaldawa/ccconfigs

2

Install the plugin

$

/plugin install experimental@ccconfigs

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Testing

Given task file path .plans/<project>/testing/NNN-task.md:

Process

Use TodoWrite to track testing validation:

☐ Validate existing tests (behavior-focused?)
☐ Check coverage of Validation checklist items
☐ Identify gaps (empty/null, boundaries, errors)
☐ Add tests for genuine gaps
☐ Run coverage (>80% statements, >75% branches)
☐ Update task status

Validate existing tests - behavior-focused? Covers Validation?
Identify gaps - empty/null inputs, boundaries, errors, race conditions, security
Add minimal tests if genuinely missing
Run coverage - verify >80% statements, >75% branches
Update task status using Edit tool:
- Find: **Status:** [current status]
- Replace: **Status:** READY_FOR_REVIEW

Append testing notes using Edit tool (add to end of task file):

**testing:**
Validated [N] tests (behavior-focused)

Added [M] edge cases:
- [Test description]
- [Test description]

Test breakdown: Unit: X | Integration: Y | Total: Z
Coverage: Statements: XX% | Branches: XX% | Functions: XX% | Lines: XX%
Full suite: XXX/XXX passing
Working Result verified: ✓ [description]

Report completion

Test Quality

Good: expect(response.status).toBe(401) (tests behavior) Bad: expect(bcrypt.compare).toHaveBeenCalled() (tests implementation)

Granularity: Pure functions → Unit | DB/API → Integration | Critical workflows → E2E (rare)

Failure Handling

If tests fail or coverage <80%:

Fix test scenarios first
If code bug found:
- Update status using Edit tool: Find **Status:** [current status] → Replace **Status:** NEEDS_FIX
- Append notes using Edit tool (append to end of file):
```
**testing:**
Found issues:
- [Specific issue]
- [Specific issue]

Requires code fixes. Moving back to implementation.
```

Completion

When testing is complete (status updated to READY_FOR_REVIEW or NEEDS_FIX):

Report: ✅ Testing complete. Status: [STATUS]

Links

GitHub Stats

1 forks

Updated 3 days ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

47.1k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

47.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

47.1k