Skip to content

docs(cli): clarify generated locator page state #42791

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Devin Rousso (dcrousso) wants to merge 1 commit into from
Closed

docs(cli): clarify generated locator page state #42791

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions ...s/playwright-core/src/tools/skills/playwright-cli/references/test-generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,12 @@ await page.getByRole('button', { name: 'Submit' }).click();
await page.locator('#submit-btn').click();
```

### Account for page state

`generate-locator` uses the current page state, and `recording-stop` returns code with locators generated when each action was recorded. A locator that is unique in a filtered or paginated view may become ambiguous in another state. Generate locators for each step's intended state, and replay the setup needed to reach it.

Start each replay from a clean initial state to avoid duplicate test data. If an action fails with `strict mode violation: ... resolved to N elements`, correct the page state or scope the locator to the intended row or region. Do not add `.first()` just to hide the ambiguity.

### Explore before recording

Take snapshots to understand the page structure before recording actions:
Expand Down
Loading