Skip to content

Fix/accessibility executescript prototype patch#3

Merged
xxshubhamxx merged 3 commits into
xxshubhamxx:release_3.11.1from
kamal-kaur04:fix/accessibility-executescript-prototype-patch
Jun 12, 2026
Merged

Fix/accessibility executescript prototype patch#3
xxshubhamxx merged 3 commits into
xxshubhamxx:release_3.11.1from
kamal-kaur04:fix/accessibility-executescript-prototype-patch

Conversation

@xxshubhamxx

Copy link
Copy Markdown
Owner

Original PR: nightwatchjs#57

kamal-kaur04 and others added 3 commits June 10, 2026 18:03
…h commands

commandWrapper() patched `originalCommand.command` directly, which only works
for web-element commands that export a plain object (`module.exports.command = fn`).
executeScript/executeAsyncScript (and the protocol/client/appium commands) export
a class with `command` on the prototype, so the patch landed on a non-existent
static method and the real prototype command Nightwatch invokes stayed unpatched.

As a result `performScan` never ran for `browser.execute('mobile:scroll', ...)`
(and all other class-based commands listed in commands.json) on App Accessibility
sessions — no accessibility scan was captured for those interactions.

Detect whether `command` lives as an own property (object export) or on the
prototype (class export) and patch the correct target, mirroring how the
`protocolAction` branch already handles class-based commands. The existing
`shouldPatchExecuteScript` recursion guard now becomes effective and prevents the
plugin's own `browserstack_executor` scan scripts from re-triggering a scan.

Verified on a real-device Android App Accessibility session: `mobile:scroll` now
triggers exactly one performScan, with no recursion, and the test passes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…r scripts

shouldPatchExecuteScript() treated any non-string script as a script to skip
(`!script || typeof script !== 'string'` -> return true), so user scripts passed
as functions — `browser.execute(function(){...})` / `executeAsyncScript(fn)` — never
triggered performScan, even though they can mutate page/screen state just like a
string script.

The plugin's own scan scripts are always strings carrying the `browserstack_executor`
token (verified: every internal execute* call in the SDK passes a string), so a
non-string script is always a user script and is safe to scan — the string-based
recursion guard is unaffected.

Treat an empty/undefined script as skip (unchanged) and a function script as a user
script to scan.

Verified on a real-device Android App Accessibility session: executeAsyncScript(fn)
now triggers exactly one performScan; the 18 internal browserstack_executor scan
scripts are still skipped (no recursion); test passes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…eScript guard

Adds unit tests for the two accessibility command-wrapping fixes:

- shouldPatchExecuteScript: empty -> skip, internal browserstack_executor /
  accessibility scripts -> skip, user string scripts -> scan, and (regression)
  function-form user scripts -> scan.
- commandWrapper: wraps the own `command` of object-export (web-element) commands
  and the prototype `command` of class-export commands (executeScript) without
  creating a phantom static; verifies the wrapped command triggers performScan,
  delegates to the original, honours the recursion guard, and scans function-form
  scripts. Drives commandWrapper deterministically by stubbing
  require.resolve('nightwatch') and injecting fake command modules via require.cache.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@xxshubhamxx xxshubhamxx merged commit 8d59ec3 into xxshubhamxx:release_3.11.1 Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants