Skip to content

Selenium and Nightwatch: native traces have no element or accessibility tree #563

Closed

Description

@vishnuv688

Problem

On a native Appium session, the Selenium and Nightwatch adapters capture only a screenshot per action. Their action-snapshot.ts wrappers pass core takeScreenshot and nothing else when native is true, while the WebdriverIO service and the Python adapter also pass a page-source reader. So a native trace from Selenium or Nightwatch has no element list, accessibility tree or locators per action.

Seen in #516: Selenium and Nightwatch native runs time only the screenshot probe.

Proposal

Pass a page-source reader on native sessions (Selenium: the unpatched getPageSource; Nightwatch: the raw WebDriver transport, as its other probes do), so core builds the same element and accessibility data it does for WebdriverIO. Add a test per adapter, and a capability-matrix row for the native element tree and accessibility tree per adapter, plus the docs-site table.

Note #516's measurements: page source is about half of an Android capture and 87% of an iOS one, so this adds capture time on native; the filmstrip change should land first or together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions