# Standardize Test Operations

Testing work often becomes inconsistent across planning, execution, and reporting. This skill helps Claude, Codex, and Claude Code guide structured test operations.

## Install

```bash
npx skillstore add a-genno/test-ops
```

## Metadata

- Status: approved
- Slug: a-genno-test-ops
- Skillstore revision: r1
- Version status: missing
- Tree hash: 2b64a6d611924192d797f4cecec97620021cf1e5d1ce7c9658d66f317c1ba265
- Author: A-Genno
- GitHub username: A-Genno
- License: MIT
- Repository: https://github.com/A-Genno/Polaris/tree/master/documents/skills/test-ops
- Ref: d46e62089a6dfc9e14ea02eebd9b8e2ad2dfe1f4
- 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
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/a-genno-test-ops
- Manifest: https://skillstore.pages.dev/api/skills/a-genno-test-ops/manifest

## Capabilities

- Outlines test design for normal, error, boundary, and edge cases.
- Recommends independent tests that can run without cross-test dependencies.
- Defines mocking guidance for databases, APIs, time-dependent code, and file I/O.
- Provides implementation steps from feature analysis through coverage review.
- Specifies test quality standards for structure, names, assertions, and error messages.

## Use Cases

- Plan Feature Test Coverage: Create a clear test plan that covers normal, error, boundary, and edge cases.
- Review Mocking Strategy: Decide how to isolate databases, APIs, clocks, timers, and file access during tests.
- Standardize Test Reports: Align test implementation and results reporting around consistent quality criteria.

## Prompt Templates

### Create a Basic Test Plan

```
Use the test-ops skill to create a test plan for this feature. Include normal, error, boundary, and edge cases.
```

### Design Isolated Tests

```
Use the test-ops skill to design independent tests for this component. Identify needed mocks and fixtures.
```

### Audit Test Quality

```
Use the test-ops skill to review these tests for independence, readability, assertions, and failure messages.
```

### Build a Coverage Improvement Plan

```
Use the test-ops skill to find coverage gaps and propose a prioritized plan to improve test completeness.
```

## Limitations

- Does not include runnable test scripts or framework-specific commands.
- Does not inspect project code without user-provided context.
- Coverage goals still require engineering judgment.
- Provides general testing guidance, not a complete QA governance process.

## Best Practices

- Provide the feature behavior, expected risks, and current test framework before asking for a plan.
- Ask for separate normal, error, boundary, and edge cases to avoid missing important scenarios.
- Review proposed mocks against real system boundaries before implementing tests.

## Anti Patterns

- Do not ask for full coverage without explaining the feature or business risk.
- Do not treat generated test plans as a substitute for running the actual test suite.
- Do not mock behavior that should be verified through integration tests.

## Security Audit

- Audited at: 2026-07-07T19:20:08.804\+00:00
- Summary: The only static finding is a high-entropy heuristic on SKILL.md. Manual review shows readable Japanese Markdown with testing guidance, so the finding is a false positive.

## Stats

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