playwright test
- Repo stars 34,831
- Author repo posthog
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @PostHog · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
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.
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.
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.
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**
Listed in source order.
sections -> 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
terms -> 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.
files/cmd -> mcp__playwright__browser_navigate · mcp__playwright__browser_click · mcp__playwright__browser_screenshot · --repeat-each 10
body sha256 -> 837d6d339b6f
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.
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 3Debug 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 10added 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