latestaiagents/test-planning
plugins/qa-testing/skills/test-strategy/test-planning/SKILL.md
Create comprehensive test strategies and test plans for software projects. Use this skill when planning testing for new features, releases, or projects. Activate when: test plan, test strategy, testing approach, QA planning, test coverage, release testing.
$ install --global
skillsauthnpx skillsauth add latestaiagents/agent-skills test-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 2:55 AM21.3s1 file scanned
SKILL.md
- name:
- test-planning
- description:
- |
- Activate when:
- test plan, test strategy, testing approach, QA planning, test coverage, release testing.
Test Planning
Create comprehensive test strategies that ensure quality and coverage.
When to Use
- Planning testing for a new feature or release
- Creating a test strategy document
- Defining test coverage requirements
- Estimating testing effort
- Setting up QA processes for a new project
Test Strategy Document Template
# Test Strategy: [Project/Feature Name]
**Version:** 1.0
**Author:** [Name]
**Date:** [Date]
**Status:** Draft / In Review / Approved
## 1. Introduction
### 1.1 Purpose
[Brief description of what this test strategy covers]
### 1.2 Scope
**In Scope:**
- [Feature/component 1]
- [Feature/component 2]
**Out of Scope:**
- [Explicitly excluded items]
### 1.3 References
- PRD: [link]
- Technical Design: [link]
- API Specs: [link]
## 2. Test Objectives
- Verify [functional requirement 1]
- Validate [performance requirement]
- Ensure [security requirement]
- Confirm [compatibility requirement]
## 3. Test Approach
### 3.1 Test Levels
| Level | Scope | Owner | Tools |
|-------|-------|-------|-------|
| Unit | Individual functions | Dev | Jest, pytest |
| Integration | API contracts | Dev/QA | Postman, SuperTest |
| E2E | User workflows | QA | Playwright, Cypress |
| Performance | Load/stress | QA | k6, Artillery |
### 3.2 Test Types
- [ ] Functional testing
- [ ] Regression testing
- [ ] Smoke testing
- [ ] Integration testing
- [ ] Performance testing
- [ ] Security testing
- [ ] Accessibility testing
- [ ] Compatibility testing
## 4. Test Environment
| Environment | Purpose | Data |
|-------------|---------|------|
| Dev | Unit/Integration | Mocked |
| Staging | E2E/Regression | Sanitized prod |
| Pre-prod | Performance/Security | Prod-like |
## 5. Test Data
### Requirements
- [Data requirement 1]
- [Data requirement 2]
### Sources
- Test data generators
- Sanitized production data
- Synthetic data sets
## 6. Entry/Exit Criteria
### Entry Criteria
- [ ] Code complete and merged
- [ ] Unit tests passing (>80% coverage)
- [ ] Environment deployed and stable
- [ ] Test data prepared
### Exit Criteria
- [ ] All critical test cases passed
- [ ] No P0/P1 bugs open
- [ ] Performance benchmarks met
- [ ] Security scan passed
- [ ] Sign-off from stakeholders
## 7. Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| [Risk 1] | High/Med/Low | High/Med/Low | [Action] |
| [Risk 2] | | | |
## 8. Schedule
| Phase | Start | End | Owner |
|-------|-------|-----|-------|
| Test Planning | | | |
| Test Case Design | | | |
| Test Execution | | | |
| Bug Fixing | | | |
| Regression | | | |
| Sign-off | | | |
## 9. Deliverables
- [ ] Test cases in [TestRail/Xray]
- [ ] Automated test suite
- [ ] Test execution report
- [ ] Bug report summary
- [ ] Sign-off document
Test Coverage Matrix
## Feature Coverage Matrix
| Feature | Unit | Integration | E2E | Performance | Security |
|---------|------|-------------|-----|-------------|----------|
| User Login | ✓ | ✓ | ✓ | ✓ | ✓ |
| Checkout | ✓ | ✓ | ✓ | ✓ | ✓ |
| Search | ✓ | ✓ | ✓ | ✓ | |
| Profile | ✓ | ✓ | ✓ | | |
## Risk-Based Priority
| Priority | Description | Coverage Target |
|----------|-------------|-----------------|
| P0 | Critical path, revenue impact | 100% |
| P1 | Core functionality | 90% |
| P2 | Important features | 70% |
| P3 | Nice-to-have | 50% |
Test Estimation
Estimation Factors
| Factor | Multiplier | Notes |
|--------|------------|-------|
| New feature | 1.5x | More exploration needed |
| Complex logic | 1.3x | More test cases |
| External integrations | 1.4x | More failure scenarios |
| Security-critical | 1.5x | Additional security tests |
| Performance-critical | 1.3x | Load testing needed |
Estimation Template
## Test Effort Estimation
| Activity | Hours | Notes |
|----------|-------|-------|
| Test case design | X | |
| Test data setup | X | |
| Manual execution | X | |
| Automation development | X | |
| Bug verification | X | |
| Regression testing | X | |
| **Total** | **X** | |
Release Testing Checklist
## Pre-Release Checklist
### Functional
- [ ] All user stories tested
- [ ] Acceptance criteria verified
- [ ] Edge cases covered
- [ ] Error handling verified
### Regression
- [ ] Core workflows passing
- [ ] No new failures in existing tests
- [ ] Cross-browser verification
### Non-Functional
- [ ] Performance benchmarks met
- [ ] Security scan completed
- [ ] Accessibility audit passed
### Documentation
- [ ] Release notes prepared
- [ ] Known issues documented
- [ ] Rollback plan in place
### Sign-off
- [ ] QA sign-off
- [ ] Product sign-off
- [ ] Engineering sign-off
Best Practices
- Risk-based testing - Focus effort on highest-risk areas
- Shift left - Involve QA early in development
- Automate wisely - Automate stable, repetitive tests
- Data independence - Tests shouldn't depend on specific data
- Environment parity - Test environments should mirror production
- Clear criteria - Define pass/fail criteria upfront
- Continuous feedback - Report status early and often
Related Skills
latestaiagents/skill-testing
development
VerifiedTrustedCommunity
Test skills for correct activation, content quality, and regression — both automated checks (frontmatter validity, lint) and manual verification (query-suite activation testing). Covers CI integration and how to catch skill regressions before users do. Use this skill when adding skills to a repo, setting up CI for a skill library, or debugging "the skill exists but doesn't work". Activate when: test skills, validate skills, skill CI, skill linting, skill activation test, skill regression.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/skill-frontmatter
documentation
VerifiedTrustedCommunity
Write the YAML frontmatter for a SKILL.md file so it activates reliably — name, description, and activation keywords that the model matches against. Covers length, tone, and the most common frontmatter mistakes. Use this skill when authoring a new skill, fixing a skill that isn't auto-activating, or reviewing skills for publication. Activate when: SKILL.md frontmatter, skill description, skill activation, skill YAML, write a skill, author a skill.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/skill-activation-patterns
development
VerifiedTrustedCommunity
Design skills that fire at the right moment — neither over-eager (noise) nor under-eager (silent). Covers activation specificity, trigger phrases, disambiguation between overlapping skills, and debugging activation. Use this skill when multiple skills could fire on the same query, a skill never fires, or a skill fires too often. Activate when: skill won't activate, skill over-activates, overlapping skills, skill triggers, skill selection, skill disambiguation.
2SKILL.mdUpdated Apr 23, 2026
latestaiagents/progressive-disclosure
development
VerifiedTrustedCommunity
Structure SKILL.md content so the model reads just enough — concise summary up front, progressively deeper detail, examples on demand. Covers section ordering, length budgets, when to split into multiple skills. Use this skill when writing or refactoring a skill body, one skill has grown too long, or a skill is wordy but not useful. Activate when: SKILL.md structure, skill content, skill too long, split skill, progressive disclosure, skill body.
2SKILL.mdUpdated Apr 23, 2026