ryan
d910a6bc65
Chore App Build, Test, and Push Docker Images / build-and-push (push) Failing after 2m29s
- Introduced detailed documentation for test generation workflow in Playwright CLI, covering planning, generating, and healing tests. - Added tracing capabilities documentation, including usage, output files, and best practices for debugging and performance analysis. - Included video recording instructions, emphasizing best practices for capturing browser automation sessions with chapter markers and overlays. - Implemented user tutorial authentication setup and tutorial tests for parent mode in the E2E testing framework. - Created JSON files for user tutorial state management, ensuring isolated test environments.
24 lines
665 B
Markdown
24 lines
665 B
Markdown
# Inspecting Element Attributes
|
|
|
|
When the snapshot doesn't show an element's `id`, `class`, `data-*` attributes, or other DOM properties, use `eval` to inspect them.
|
|
|
|
## Examples
|
|
|
|
```bash
|
|
playwright-cli snapshot
|
|
# snapshot shows a button as e7 but doesn't reveal its id or data attributes
|
|
|
|
# get the element's id
|
|
playwright-cli eval "el => el.id" e7
|
|
|
|
# get all CSS classes
|
|
playwright-cli eval "el => el.className" e7
|
|
|
|
# get a specific attribute
|
|
playwright-cli eval "el => el.getAttribute('data-testid')" e7
|
|
playwright-cli eval "el => el.getAttribute('aria-label')" e7
|
|
|
|
# get a computed style property
|
|
playwright-cli eval "el => getComputedStyle(el).display" e7
|
|
```
|