# Build Complete Testing Strategies

Teams often miss coverage gaps, unclear test ownership, and weak release gates. This skill provides structured plans, templates, and checklists for reliable software testing.

## Install

```bash
npx skillstore add ai agent hub/ariegoldkin-testing-strategy-builder
```

## Metadata

- - Slug: ariegoldkin-testing-strategy-builder
- - Version: 1.0.0
- - Author: AI Agent Hub
- - GitHub username: ArieGoldkin
- - License: MIT
- - Repository: https://github.com/ArieGoldkin/ai-agent-hub/tree/main/skills/testing-strategy-builder
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: external\_commands, network, filesystem
- - Quality score: 74
- - Public page: https://skillstore.pages.dev/skills/ariegoldkin-testing-strategy-builder
- - Manifest: https://skillstore.pages.dev/api/skills/ariegoldkin-testing-strategy-builder/manifest

## Capabilities

- Defines coverage targets for unit, integration, end-to-end, performance, and security testing.
- Provides a reusable test plan template for scope, environments, schedules, metrics, and approvals.
- Provides a test case template with preconditions, steps, validation checkpoints, and execution history.
- Offers example test patterns for Jest, Playwright, Supertest, k6, fixtures, factories, and mocking.
- Includes a coverage checklist for static analysis, APIs, databases, user journeys, and release gates.
- Helps prioritize tests with risk-based coverage guidance for critical and lower-risk features.

## Use Cases

- Plan Tests For A New Feature: Create a test plan with scope, risk levels, coverage targets, test types, and release criteria before implementation begins.
- Improve Coverage In An Existing App: Use the checklist to find missing unit, integration, end-to-end, performance, accessibility, and security test areas.
- Standardize Test Case Documentation: Create consistent test cases with preconditions, steps, expected results, validation checkpoints, defects, and sign-off records.

## Prompt Templates

### Create A Basic Test Plan

```
Create a test plan for this feature: [feature]. Include scope, test types, coverage targets, environments, and exit criteria.
```

### Find Coverage Gaps

```
Review this project summary and identify likely testing gaps. Separate gaps by unit, integration, end-to-end, performance, security, and accessibility tests.
```

### Write Risk-Based Test Cases

```
Create risk-based test cases for [workflow]. Include critical, high, medium, and low priority scenarios with expected results.
```

### Design A Full Testing Strategy

```
Design a complete testing strategy for [application]. Include tooling, test data, CI gates, coverage metrics, ownership, reporting, and rollout risks.
```

## Limitations

- It provides guidance and templates, not an automated test runner.
- Users must adapt examples to their framework, architecture, and compliance requirements.
- Coverage targets are recommendations and may not fit every product risk profile.
- Sample commands and code should be reviewed before use in production pipelines.

## Best Practices

- Start with risk-based priorities, then assign coverage targets to critical paths and lower-risk areas.
- Keep tests focused on behavior, observable results, and clear assertions instead of implementation details.
- Run fast checks on every commit and reserve slower end-to-end or performance suites for pull requests and releases.

## Anti Patterns

- Do not treat high coverage as proof that important user workflows are safe.
- Do not build large tests that mix setup, many workflows, and unrelated assertions.
- Do not copy sample commands or test data into production systems without review.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T10:37:20.866\+00:00
- - Summary: Static analysis flagged many shell, network, filesystem, and weak-crypto patterns, but reviewed evidence shows they are Markdown examples, templates, and testing guidance rather than executable skill logic. No prompt-injection language, data exfiltration intent, or malicious automation was found in the reviewed files. The skill is suitable for publication with low risk because users may copy commands or sample tests into their own projects.

## Stats

- - Views: 355
- - Downloads: 7
- - Favorites: 1
- - Popularity score: 0