Test Plan【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwrightApplication OverviewTest Scenarios1.Seed:tests/seed.spec.ts1.1.File:tests/group/kebab-case-scenario-name.spec.tsSteps:expect:expect:expect:1.2....2.Seed:tests/seed.spec.ts...编写规范 - 每个场景相互独立都从 seed 的干净状态出发 —— **绝不串联场景** - 场景名使用 kebab-case且与测试文件名一致should-add-single-todo → should-add-single-todo.spec.ts - 覆盖 happy path、边界、校验、负向流程与持久化 - 步骤写在**用户层面**如 Type Buy milk into the input不要写 API 层面如 call fill - 可观测结果放进 - expect: 列表项 —— 生成阶段每条 expect 都会变成一条断言。 ## 2. Generate把 spec 变成测试 **目标**读取 spec 文件产出 Playwright 测试文件若 spec 与实际应用已有漂移可选择同步更新 spec。 ### 2.1 输入 - **Spec 文件**例如 specs/basic-operations.plan.md - **目标范围**单条场景如 1.2、整个分组1或全部 - **Seed 文件**从场景所属分组的 **Seed:** 行读取。 ### 2.2 生成单条场景 对每个目标场景**依序**逐个生成**绝不并行** —— 场景共享同一个 seed 会话 bash PLAYWRIGHT_HTML_OPENnever npx playwright test seed-file --debugcli # background playwright-cli attach tw-XXXX # resume同样地不要直接用playwright-cli打开应用 URL始终经过测试以捕获自定义初始化。接下来逐条走 spec 的Steps:把 spec 当作计划、把活的应用当作事实来源。如果某一步含糊click the button——哪个 button、指向的元素已不存在、或与应用实际行为矛盾应运用判断力先把 spec 改成应用真实的样子再继续走。在生成中途编辑 spec 是预期内行为。每条动作都会打印等价的 Playwright TypeScript机制见第 0 节playwright-cli snapshot # find refs playwright-cli fill e3 John Doe # - page.getByRole(textbox, {...}).fill(...) playwright-cli press Enter playwright-cli click e7对 spec 里每条- expect:列表项都要添加显式断言。随后把生成的代码收集起来写到 spec 指定路径的测试文件// spec: specs/basic-operations.plan.md // seed: tests/seed.spec.ts import { test, expect } from ./fixtures; // or playwright/test if no fixtures file test.describe(Signing in and out, () { test(should sign in, async ({ page }) { // 1. Navigate to the application // (handled by the seed fixture) // 2. Type John Doe into the username field await page.getByRole(textbox, { name: username }).fill(John Doe); // 3. Type password await page.getByRole(textbox, { name: password }).fill(TestPassword); // 4. Press Enter to submit await page.getByRole(textbox, { name: password }).press(Enter); await expect(page.getByRole(heading)).toContainText(Welcome, John Doe!); }); });生成规则一个测试一个文件。文件路径、describe 名与 test 名均照抄 spec去掉序号前缀每个带编号的步骤在其动作前加一行// N. step text注释describe 分组名照抄 spec 中的分组名不加1.序号项目有 fixtures 文件就import ... from ./fixtures否则从playwright/test导入重要进入下一个场景前先关闭 CLI 会话并停止后台测试。2.3 生成多条场景循环执行 2.2一次处理一个目标场景并在每个场景之间重启 seed保证每个测试都从干净的页面开始。由于每次生成的会话名唯一tw-XXXX这条流程可以安全并行——但务必保证每个测试运行都被停止。2.4 运行生成的测试生成完毕后把新测试跑一遍PLAYWRIGHT_HTML_OPENnever npx playwright test tests/group/scenario.spec.ts任何失败都会进入第 3 节处理。3. Heal诊断、修复、对账目标修复失败的测试如果应用的预期行为本身发生了变化同步更新 spec。3.1 找出失败用例PLAYWRIGHT_HTML_OPENnever npx playwright test记录失败的file:line清单一次只处理一个。不要尝试并行修复——共享状态与单一 CLI 会话使并行非常脆弱。3.2 调试单个失败在后台以 debug 模式运行单个失败测试再 attachPLAYWRIGHT_HTML_OPENnever npx playwright test tests/group/scenario.spec.ts:line --debugcli # wait for Debugging Instructions and the tw-XXXX session name playwright-cli attach tw-XXXX测试在起点暂停。逐步执行或运行到失败动作 / 断言的前一刻然后开始诊断playwright-cli snapshot # did the element change / move / rename? playwright-cli console # app-side errors? playwright-cli requests # failed request? wrong payload? playwright-cli show --annotate # ask the user to point somewhere【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwright创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考