测试批判性思维
当需要挑战已有假设、挖掘隐含约束、发现"所有人都没想过"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如"用户一定会有网络"、"输入一定有内容"、"操作顺序一定正确"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为"正常"的异常场景。每一个测试场景都应该走一遍"如果这个假设不成立呢"的质疑流程。 本技能属于 QA Test Skills 技能集(49 个技能之一),完整工作流体验需安装全套:npx skills add Kokxi/qa-
as observed 2026-09-02T06:49:02.991ZWant 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-critical-thinking- 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)
- 3
- Weekly downloads (upstream)
- 754
Observation history
2026-09-02T06:49:02.991Z
Fields that differed: changelog description displayName latestVersion summary
| Field | Before | After |
|---|---|---|
changelog |
"1.7.5: 版本号升级" | "显示名改中文" |
description |
"当需要挑战已有假设、挖掘隐含约束、发现\"所有人都没想过\"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如\"用户一定会有网络\"、\"输入一定有内容\"、\"操作顺序一定正确\"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为 | "当需要挑战已有假设、挖掘隐含约束、发现\"所有人都没想过\"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如\"用户一定会有网络\"、\"输入一定有内容\"、\"操作顺序一定正确\"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为 |
displayName |
"qa-critical-thinking" | "测试批判性思维" |
latestVersion |
"1.7.5" | "1.7.6" |
summary |
"当需要挑战已有假设、挖掘隐含约束、发现\"所有人都没想过\"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如\"用户一定会有网络\"、\"输入一定有内容\"、\"操作顺序一定正确\"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为 | "当需要挑战已有假设、挖掘隐含约束、发现\"所有人都没想过\"的测试场景时使用此技能。测试中最常犯的错误是接受了需求文档里的隐含假设——比如\"用户一定会有网络\"、\"输入一定有内容\"、\"操作顺序一定正确\"。用「如果不呢」的深度质疑方式反向思考,暴露那些被默认为 |
2026-08-31T05:56:02.339Z
Fields that differed: changelog latestVersion
| Field | Before | After |
|---|---|---|
changelog |
"- Added more advanced critical thinking exercises to the documentation, covering scenarios like concurrency, state transitions, and cross-system contracts.\n- Introduced new | "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.