Playwright 测试
- 作者仓库星标 34,831
- 作者仓库 posthog
Read @playwright/README.md for best practices, gotchas, and how to run tests.
Rules
- Follow the best practices in the README strictly
- After UI interactions, always assert on UI changes, do not assert on network requests resolving
- Keep looping until all tests pass. Do not give up or ask the user for help. You must resolve every failure yourself.
Instructions
You are to plan an end to end playwright test for a feature.
Step 1: Plan the test(s) to be done.
Use the Playwright MCP tools (e.g., mcp__playwright__browser_navigate, mcp__playwright__browser_click, mcp__playwright__browser_screenshot) to interact with the browser and plan your tests.
After your exploration, present the plan to me for confirmation or any changes.
Step 2: Implement the test plan
- Write the tests, making sure to use common patterns used in neighbouring files.
- Run the tests with
BASE_URL='http://localhost:8010' pnpm --filter=@posthog/playwright exec playwright test <file name> --retries 0 --workers 3 - Debug any failures. Look at screen shots, if needed launch the playwright mcp skills to interact with the browser. Go back to step 1 after attempting a fix.
Step 3: Ensure no flaky tests
After all tests pass in the file, run with --repeat-each 10 added to the command. This will surface any flaky tests.
If any test fails across the 10 runs, treat it as a real failure: go back to Step 2, debug, fix, and re-run Step 3. Do not proceed to Step 4 until every run of every test passes.
Step 4: Report
Once all tests pass, output a single line: Testing Complete
- 流狐分类
- AI 智能
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @PostHog · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Use the Playwright MCP tools (e.g., mcpplaywrightbrowsernavigate, mcpplaywrightbrowserclick, mcpplaywrightbrowserscreenshot) to interact with the browser and plan your tests. After your exploration, present the plan to me for confirmation or any changes.
Write the tests, making sure to use common patterns used in neighbouring files. Run the tests with BASEURL='http://localhost:8010' pnpm --filter=@posthog/playwright exec playwright test <file name> --retries 0 --workers 3
After all tests pass in the file, run with --repeat-each 10 added to the command. This will surface any flaky tests. If any test fails across the 10 runs, treat it as a real failure: go back to Step 2, debug, fix, and re-run Step 3. Do not proceed to Step 4…
Once all tests pass, output a single line: Testing Complete
Read @playwright/README.md for best practices, gotchas, and how to run tests.
## Rules
- Follow the best practices in the README strictly
- After UI interactions, always assert on UI changes, do not assert on network requests resolving
- **Keep looping until all tests pass.** Do not give up or ask the user for help. You must resolve every failure yourself.
## Instructions
You are to plan an end to end playwright test for a feature.
### Step 1: Plan the test(s) to be done.
Use the Playwright MCP tools (e.g., `mcp__playwright__browser_navigate`, `mcp__playwright__browser_click`, `mcp__playwright__browser_screenshot`) to interact with the browser and plan your tests.
After your exploration, present the plan to me for confirmation or any changes.
### Step 2: Implement the test plan
- Write the tests, making sure to use common patterns used in neighbouring files.
- Run the tests with `BASE_URL='http://localhost:8010' pnpm --filter=@posthog/playwright exec playwright test <file name> --retries 0 --workers 3`
- Debug any failures. Look at screen shots, if needed launch the playwright mcp skills to interact with the browser. Go back to step 1 after attempting a fix.
### Step 3: Ensure no flaky tests
After all tests pass in the file, run with `--repeat-each 10` added to the command. This will surface any flaky tests.
If any test fails across the 10 runs, treat it as a real failure: go back to Step 2, debug, fix, and re-run Step 3. Do not proceed to Step 4 until every run of every test passes.
### Step 4: Report
Once all tests pass, output a single line: **Testing Complete**作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Rules → Instructions → Step 1: Plan the test(s) to be done. → Step 2: Implement the test plan → Step 3: Ensure no flaky tests → Step 4: Report
要点 -> Keep looping until all tests pass. · Testing Complete · Read @playwright/README.md for best practices, gotchas, and how to run tests. · You are to plan an end to end playwright test for a feature. · After your exploration, present the plan to me for confirmation or any changes. · - Write the tests, making sure to use common patterns used in neighbouring files. · After all tests pass in the file, run with --repeat-each 10 added to the command. · If any test fails across the 10 runs, treat it as a real failure: go back to Step 2, debug, fix, and re-run Step 3.
文件/命令 -> mcpplaywrightbrowsernavigate · mcpplaywrightbrowserclick · mcpplaywrightbrowserscreenshot · --repeat-each 10
内容 SHA-256 -> 837d6d339b6f
方法与流程
适用与边界
原文中的明确线索
mcpplaywrightbrowsernavigate、mcpplaywrightbrowserclick、mcpplaywrightbrowserscreenshot、--repeat-each 10