TheBotique

组合测试策略

当参数多、环境多、"全组合测不完"时运用正交试验法、Pairwise和判定表来解决组合爆炸问题。如果系统有多个输入字段的组合依赖关系(如"A=1且B=2时C不能为3")、或者需要适配多浏览器多操作系统多语言,一定要用此技能来设计高效的组合覆盖方案。不要试图全覆盖——组合测试的核心是用最少的用例达到最高的组合覆盖率。输出组合覆盖矩阵并标注覆盖遗漏。 本技能属于 QA Test Skills 技能集(49 个技能之一),完整工作流体验需安装全套:npx skills add Kokxi/qa-test-skills

as observed 2026-09-02T06:49:02.991Z

Want to know when this changes? Sign in with an email address and we will tell you. Free, no card, watch up to 5.

Identifier
qa-combination-strategy
Source
ClawHub
Version observed
1.7.6
Source repository
not published
Repository observation
No source repository listed
First observed here
2026-08-28T22:54:43.883Z
Observations recorded
3
Installs (reported upstream)
2
Weekly downloads (upstream)
660

Observation history

2026-09-02T06:49:02.991Z

Fields that differed: changelog description displayName latestVersion summary

FieldBeforeAfter
changelog "1.7.5: 版本号升级" "显示名改中文"
description "当参数多、环境多、\"全组合测不完\"时运用正交试验法、Pairwise和判定表来解决组合爆炸问题。如果系统有多个输入字段的组合依赖关系(如\"A=1且B=2时C不能为3\")、或者需要适配多浏览器多操作系统多语言,一定要用此技能来设计高效的组合覆盖方案。不要试图全覆盖——组合测试的核心是用最少的用例达到最 "当参数多、环境多、\"全组合测不完\"时运用正交试验法、Pairwise和判定表来解决组合爆炸问题。如果系统有多个输入字段的组合依赖关系(如\"A=1且B=2时C不能为3\")、或者需要适配多浏览器多操作系统多语言,一定要用此技能来设计高效的组合覆盖方案。不要试图全覆盖——组合测试的核心是用最少的用例达到最
displayName "qa-combination-strategy" "组合测试策略"
latestVersion "1.7.5" "1.7.6"
summary "当参数多、环境多、\"全组合测不完\"时运用正交试验法、Pairwise和判定表来解决组合爆炸问题。如果系统有多个输入字段的组合依赖关系(如\"A=1且B=2时C不能为3\")、或者需要适配多浏览器多操作系统多语言,一定要用此技能来设计高效的组合覆盖方案。不要试图全覆盖——组合测试的核心是用最少的用例达到最 "当参数多、环境多、\"全组合测不完\"时运用正交试验法、Pairwise和判定表来解决组合爆炸问题。如果系统有多个输入字段的组合依赖关系(如\"A=1且B=2时C不能为3\")、或者需要适配多浏览器多操作系统多语言,一定要用此技能来设计高效的组合覆盖方案。不要试图全覆盖——组合测试的核心是用最少的用例达到最
2026-08-31T05:56:02.339Z

Fields that differed: changelog latestVersion

FieldBeforeAfter
changelog "- Added slug and displayName fields to metadata for standardization.\n- Incremented version to 1.6.3.\n- skill-card.md removed from the project.\n- No changes to skill logic "1.7.5: 版本号升级"
latestVersion "1.6.3" "1.7.5"

Correction

If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.