Pdlc e2e
端到端测试（生成或执行 E2E 用例）From its SKILL.md
npx -y skills add kanfu-panda/pdlc-skills --skill pdlc-e2eAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 493 tokens by cl100k_base, as published. Nobody here has run it
端到端测试
<!-- @include templates/prompts/iron-law.md -->编写端到端（E2E）测试用例，验证完整的用户操作流程。
工作流程
- 阅读需求文档: 阅读
docs/01_requirements/user-stories/下的用户故事和验收标准 - 阅读 UI 设计: 阅读
docs/02_design/ui-ux/下的 UI 设计文档 - 梳理测试场景: 按用户旅程梳理核心操作路径
- 编写测试计划: 在
docs/04_testing/e2e-tests/下补充 E2E 测试用例 - 编写测试代码: 使用项目对应的 E2E 框架编写自动化测试
- 运行验证: 确保测试可通过
测试场景设计
- 核心路径（P0）: 必须通过，如登录→主流程→结果验证
- 分支路径（P1）: 常见的备选操作路径
- 异常路径（P2）: 网络错误、超时、权限不足等异常场景
- 边界场景（P3）: 空数据、超长输入、并发操作
测试框架（根据前端技术栈）
- React/Vue/Next.js: Playwright 或 Cypress
- 微信小程序: miniprogram-automator
- API 层: 直接用 HTTP 请求库
要求
<!-- @include templates/prompts/output-language.md -->- 测试用例命名格式:
应该_当<条件>时_<预期行为> - 测试数据独立，不依赖其他测试的执行结果
- 每个测试结束后清理数据
测试目标: $ARGUMENTS
<!-- @include templates/prompts/state-update.md --> <!-- @include templates/prompts/handoff.md -->What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most e2e browser skills give in 493 tokens
Counted across 499 of the 513 authors here whose files we hold, read 2026-09-06
- Capture screenshots, videos, and traces on failurein 32 of 499, across 23 files
- Close the browser when donein 22 of 499
- Interact with elements using snapshot refsin 21 of 499, across 20 files
- Wait for specific network responses instead of fixed timeoutsin 20 of 499, across 10 files
- Keep tests independent with no shared statein 19 of 499, across 17 files
- Use Page Object Model classes to encapsulate page interactionsin 19 of 499, across 9 files
- Locate elements with data-testid attributesin 19 of 499, across 10 files
- Quarantine flaky tests with fixme or skipin 17 of 499, across 7 files
- Upload test artifacts after every CI runin 17 of 499, across 8 files
- Wait on conditions instead of using fixed sleepsin 17 of 499, across 13 files
- Clean up test data after each testhere, and in 17 of 499, across 16 files
- Test user-visible behavior, not implementation detailsin 16 of 499, across 10 files
Said here and by no other author read
- read user stories and acceptance criteria first
- read the UI design documents
- organize test scenarios by user journey
- write E2E test case documents
- cover core, branch, exception, and boundary scenarios
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.