Test Strategy
petrkindlmann/qa-skills/skills/test-strategy作者 petrkindlmannb3bb61bd268bMIT168 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫4 個月前更新
Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.
新增到 SourceWeft 工作區
- 在儀表板中開啟該技能，並將它新增到工作區。
- 為需要使用它的對話啟用該技能。
該技能僅含說明：不附帶任何可執行的腳本。
新增到 SourceWeft系統會先要求你登入，然後直接帶你回到這個技能。
讓你的代理程式來安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 或其他能執行命令的代理程式中，也可以貼上到 SourceWeft 對話裡。代理程式會閱讀這個技能的安裝說明，向你展示它的來源、授權條款和腳本情況，在你同意後用 SourceWeft CLI 安裝。
閱讀 https://sourceweft.com/skills/gh-petrkindlmann-qa-skills-test-strategy/install.md 中的說明，按說明安裝這個技能。安裝前先告訴我它的來源、授權條款以及是否附帶腳本，等我確認。修改我電腦上的其他任何內容之前也要先問我。用命令列自行安裝
適用於 Claude Code、Codex、Cursor 及其他本機代理程式。SourceWeft CLI 會從原始碼儲存庫中取得此處掃描過的那次提交，並根據掃描時記錄的雜湊值逐一驗證每個檔案。只要有任何不一致，就不會寫入任何內容。
npx @sourceweft/cli skills install @petrkindlmann/test-strategy新增 --agent claude-code、codex、cursor 或 universal 來選擇安裝給哪個代理程式（預設為 Claude Code）。
上游安裝器——未經 SourceWeft 驗證
開源的 skills 安裝器會取得同一個固定的提交，但不會根據 SourceWeft 記錄的雜湊值驗證檔案。
npx skills add https://github.com/petrkindlmann/qa-skills/tree/b3bb61bd268b147476252c6ed5a0440c87b97441/skills/test-strategy來源與署名
來源：petrkindlmann/qa-skills位於skills/test-strategy提交b3bb61b
授權條款： MIT
內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。
更多來自 petrkindlmann/qa-skills 的技能
Visual Testing
petrkindlmann
指導使用 Playwright 截圖以及 Chromatic、Percy、Argos CI 等託管工具進行視覺回歸測試。
Unit Testing
petrkindlmann
指導使用 Jest、Vitest 與 pytest 撰寫有效的單元測試，涵蓋測試替身、覆蓋率門檻、快照、假計時器與突變測試。
Test Suite Curation
petrkindlmann
Audit a whole regression suite and prune/restructure it with evidence: per-test coverage fingerprinting, AST near-duplicate clustering, CI-history mining for never-failing and flaky tests, prune decision rules (redundant/obsolete/low-value/keep), smoke/core/extended tiering by risk and defect-detection history, and a defensible "what we deleted and why" record. Deletion is destructive — quarantine and human sign-off are mandatory. Use when: "audit the test suite," "prune redundant tests," "find duplicate tests," "which tests can we delete," "restructure into smoke/core/extended," "is this test pulling its weight," "shrink the regression suite." Not for: Judging whether an individual test is WELL-WRITTEN (smells, assertions) — that is ai-qa-review. Healing one flaky test at runtime — that is test-reliability. Bulk selector regeneration after a UI refactor — that is selector-drift-recovery. Related: ai-qa-review, coverage-analysis, test-reliability, risk-based-testing, qa-project-context.
Test Planning
petrkindlmann
為單一衝刺或發佈建立一頁式測試計畫，涵蓋涵蓋映射、工作量估算、優先順序排序、資源分配與排程。
Test Migration
petrkindlmann
指導測試套件在不同框架之間增量移轉，例如 Selenium、Cypress 或 Jest 移轉到 Playwright 或 Vitest，並支援平行 CI。
Test Data Management
petrkindlmann
指導使用工廠、測試資料檔與合成產生方式來建立、植入、匿名化及清理具確定性且相互隔離的測試資料。