# Review Testing Strategy and Test Quality

Poor test plans miss important behavior and create brittle suites. This skill helps Claude, Codex, and Claude Code review tests, choose frameworks, and focus coverage on valuable user flows.

## Install

```bash
npx skillstore add danielpodolsky/testing-fundamentals
```

## Metadata

- Status: approved
- Slug: danielpodolsky-testing-fundamentals
- Skillstore revision: r1
- Version status: missing
- Tree hash: 87e9fe5203ce71e13a41a1bc12ad66278a7a0e3a63870a220e29ebd10cd7f046
- Author: DanielPodolsky
- GitHub username: DanielPodolsky
- License: MIT
- Repository: https://github.com/DanielPodolsky/mentor-spec/tree/main/.claude/skills/fundamentals/testing
- Ref: 34f316ba14ef36c7a620fc09f2676d2429997a77
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/danielpodolsky-testing-fundamentals
- Manifest: https://skillstore.pages.dev/api/skills/danielpodolsky-testing-fundamentals/manifest

## Capabilities

- Explains when to use unit, integration, and end-to-end tests.
- Recommends Vitest, React Testing Library, Playwright, pytest, and go test by stack.
- Identifies common test anti-patterns such as over-mocking and brittle selectors.
- Suggests behavior-focused test questions for code reviews and mentoring.
- Provides Arrange, Act, Assert structure and naming guidance for test cases.

## Use Cases

- Coach Test Planning: Guide junior developers through valuable test coverage, edge cases, and review questions.
- Review Frontend Tests: Evaluate React tests for behavior focus, semantic queries, and balanced mocking.
- Set Release Coverage: Choose high-value unit, integration, and E2E tests before shipping a feature.

## Prompt Templates

### Review a Test File

```
Use testing-fundamentals to review this test file for behavior focus, brittle selectors, and missing edge cases.
```

### Create a Coverage Plan

```
Use testing-fundamentals to create a test plan for this feature. Separate unit, integration, and end-to-end coverage.
```

### Improve Brittle Tests

```
Use testing-fundamentals to improve this test suite. Reduce over-mocking and keep tests focused on user-visible behavior.
```

### Audit Release Strategy

```
Use testing-fundamentals to audit our testing strategy for this release. Identify coverage gaps, framework fit, and high-value E2E flows.
```

## Limitations

- It does not run tests or inspect runtime results by itself.
- It focuses on testing strategy, not full security or performance review.
- Framework recommendations are concise and may need project-specific adjustment.
- It gives examples, but it does not generate complete test suites for every stack.

## Best Practices

- Prioritize tests that prove important user behavior and failure states.
- Keep most coverage in fast unit tests, then add integration and E2E tests for key flows.
- Mock external boundaries, but keep business logic and component behavior real when practical.

## Anti Patterns

- Do not chase 100 percent coverage with low-value tests.
- Do not test framework internals or third-party libraries.
- Do not rely on CSS classes, large snapshots, or internal state for assertions.

## Security Audit

- Audited at: 2026-07-06T09:56:09.578\+00:00
- Summary: All static findings were adjudicated as false positives. The external command hits are Markdown fenced diagrams and testing examples, not executable code, and no prompt injection or malicious intent was found in SKILL.md.

## Stats

- Views: 258
- Downloads: 9
- Favorites: 0
- Popularity score: 0