qa-test-strategy
Skill0 starsChanged 25 days agoMITView on GitHub
Create balanced automated test portfolios including unit, contract, integration, security, failure and performance checks. Use when planning test coverage or regression prevention.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- jianjian12138/test-skillstheir own version, first seen Oct 25, 2026
- romangalaxys10-spec/fabletheir own version, first seen Oct 13, 2026
- AZANIR/qa-skillstheir own version, first seen Mar 23, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- romangalaxys10-spec/fable★ 4same name
- AZANIR/qa-skills★ 2same name
- jianjian12138/test-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-api-engineerSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- frontend-design-directionSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- playwright-webapp-testingSkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- software-architectSkill
- technical-project-orchestratorSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use deterministic data and reliable setup/teardown.
- Distinctive: line 16
Do not describe proposed tests as passed tests.
- Very specific: line 20
Use examples/reference-platform/tests for invariant/negative/concurrency tests, examples/frontend-rtl/ui.test.mjs for pure UI-state tests …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Risk-based automated testing
- Identify business-critical journeys and consequences of failure. Prioritize money, access, data integrity, customer-facing continuity and integrations.
- Inventory existing test runners, fixtures, CI time budget and coverage gaps from repository evidence.
- Define a layered strategy: fast unit tests for rules, contract/integration tests for boundaries, E2E for essential journeys.
- Include negative tests, validation, permissions, retry/idempotency, concurrency, timeout, timezone/localization and migration compatibility where relevant.
- Use deterministic data and reliable setup/teardown. Distinguish mocks from real integration; minimize flaky sleeps.
- Capture command, environment, commit and pass/fail/not-run for every executed check.
- Define quality gates proportional to risk, not arbitrary 100% coverage targets. Identify what remains untested.
Output: test pyramid/matrix, test IDs, fixture needs, CI stages, execution evidence and next high-value tests. Do not describe proposed tests as passed tests.
Runnable example portfolio
Use examples/reference-platform/tests for invariant/negative/concurrency tests, examples/frontend-rtl/ui.test.mjs for pure UI-state tests and examples/observability-gate/test_gate.py for deterministic quality checks. Add request/contract/browser tests separately for a full test pyramid. Record test runner output, commit and environment; never claim E2E coverage from pure function tests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.