Back to Details

data-driven-testing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Deprecated

已废弃

This skill has been replaced by testing-best-practices.
Use 
testing-best-practices
for all test design, test case generation, and test strategy work.
此技能已被testing-best-practices取代。
所有测试设计、测试用例生成和测试策略工作请使用
testing-best-practices
。

What changed

变更内容

  • Test layering policy (unit / integration / e2e) replaces the unit-only DDT focus.
  • Markdown tables replace the rigid canonical JSON test-case schema.
  • Output is strategy + matrix + implementation plan, not JSON blocks.
  • Added: hard rules against fabricated fixtures and invented source locations.
  • Added: e2e execution guidance (preflight, async polling, flake handling).
  • Added: CI lane guidance (PR smoke vs nightly full).
  • Auth-state reuse and idempotent/state-tolerant e2e are first-class concerns.
  • 测试分层策略（unit / integration / e2e）取代了仅聚焦单元测试的DDT方法。
  • Markdown表格取代了僵化的标准JSON测试用例架构。
  • 输出内容为策略 + 矩阵 + 实施计划，而非JSON块。
  • 新增：禁止虚构测试固件和编造源码位置的硬性规则。
  • 新增：e2e执行指导（预检、异步轮询、处理不稳定测试）。
  • 新增：CI流水线指导（PR冒烟测试 vs 夜间全量测试）。
  • 认证状态复用和幂等/状态兼容的e2e测试成为核心关注点。