testing-strategy
Build a Complete Testing Strategy
Inconsistent test coverage allows regressions to reach users. This skill structures unit, integration, and end-to-end testing with Vitest, Playwright, coverage targets, and CI guidance.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "testing-strategy" from https://skillstore.io/skills/atman36-testing-strategy.md and its manifest at https://skillstore.io/api/skills/atman36-testing-strategy/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "testing-strategy". Plan tests for a profile component that loads user data.
Expected outcome:
- Unit coverage verifies loading, success, empty, and error states.
- Integration coverage mocks the user API and confirms rendered profile details.
- Assertions focus on accessible text and roles instead of implementation details.
Using "testing-strategy". Create an E2E strategy for sign-up and login.
Expected outcome:
- Cover account creation, logout, successful login, invalid credentials, and redirects.
- Use isolated test accounts and stable accessible selectors.
- Capture traces on retry and run the critical flow in desktop and mobile profiles.
Using "testing-strategy". Recommend CI quality gates for a TypeScript repository.
Expected outcome:
Run linting, type checks, unit coverage, and critical Playwright flows. Upload coverage and browser reports for review after failures.
Security Audit
SafeAll 79 static findings are false positives caused by Markdown syntax, documented commands, test URLs, and standard CI checks. SKILL.md contains guidance and examples without secret access, exfiltration, prompt injection, or reconnaissance behavior.
Risk Factors
⚙️ External commands (50)
🌐 Network access (3)
🔑 Env variables (8)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/atman36-testing-strategy/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/atman36-testing-strategy?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/atman36-testing-strategy?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/atman36-testing-strategy/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/atman36-testing-strategy.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
AI-Vibe-Prompts. (2026). testing-strategy security audit report (audit version 9) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/atman36-testing-strategy/audits/9BibTeX citation
@techreport{ai-vibe-prompts-atman36-testing-strategy-2026,
author = {AI-Vibe-Prompts},
title = {testing-strategy security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/atman36-testing-strategy/audits/9},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "testing-strategy security audit report (audit version 9)"
version: "1.0.0"
type: report
authors:
- name: "AI-Vibe-Prompts"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/atman36-testing-strategy/audits/9"
identifiers:
- type: other
value: "skillstore:atman36-testing-strategy:audit:9"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
atman36-testing-strategy
2026-08-21
doyajin174-testing-strategy
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add tests to a React feature
Create focused unit and integration coverage for components, interactions, error states, and mocked dependencies.
Protect critical browser journeys
Design Playwright tests for authentication, checkout, or other important workflows across desktop and mobile profiles.
Standardize repository quality gates
Define coverage thresholds, test scripts, file conventions, and CI jobs for consistent team practices.
Try These Prompts
Set up Vitest for my React TypeScript project. Include required dependencies, configuration choices, setup files, scripts, and one simple component test.
Create a testing plan for [feature]. Separate unit and integration cases, identify mocks, cover success and error states, and suggest clear test names.
Design Playwright coverage for [user journey]. Include setup, test data, desktop and mobile projects, stable selectors, assertions, retries, traces, and CI execution.
Audit this repository testing approach. Identify coverage gaps, brittle patterns, duplicated effort, missing quality gates, and propose a prioritized unit, integration, and E2E roadmap.
Best Practices
- Prioritize business logic, edge cases, user interactions, and critical workflows.
- Keep tests focused, descriptive, deterministic, and independent from external services.
- Use coverage as a gap indicator alongside meaningful behavioral assertions.
Avoid
- Do not test framework internals, third-party libraries, or trivial generated code.
- Do not use vague names or combine unrelated behaviors in one test.
- Do not rely on live services, shared state, fixed delays, or unstable selectors.
Frequently Asked Questions
Which test types does this skill cover?
Does it support non-React projects?
What coverage target does it recommend?
Can it configure continuous integration?
Will it run tests automatically?
How should E2E tests be selected?
Developer Details
Author
AI-Vibe-PromptsLicense
MIT
Author version
v1.0.0
Skillstore revision
r2
Repository
https://github.com/Atman36/AI-Vibe-Prompts/tree/main/.claude/skills/workflow/testing-strategyRef
89edfdc710d0846129dcee6a929477b04f08052c
Maintenance freshness
7/24/2026
Usage
7 downloads · 278 views
File structure
📄 SKILL.md