POC: Support multi-remote take 2

[dprevost-LMI]

Multi-Remote Support

Support multi-remote for Browser and element matchers.
Fixes #106

Browser Matchers

await expect(multiRemoteBrowser).toHaveTitle('WebdriverJS Testpage')
await expect(multiRemoteBrowser).toHaveTitle({
    chrome: expect.stringContaining('WebdriverJS'),
    firefox: expect.stringContaining('WebdriverJS')
})
await expect(multiRemoteBrowser.select('firefox')).toHaveTitle({
    firefox: expect.stringContaining('WebdriverJS')
})

Element(s) Matchers

toBe Matchers

await expect(multiRemoteBrowser.$('h1')).toBeDisplayed()
await expect(multiRemoteBrowser.$$('h1')).toBeDisplayed()

// Allow a subset of browsers
await expect(multiRemoteBrowser.$('h1').select('firefox')).toBeDisplayed()
await expect(multiRemoteBrowser.select('firefox').$$('h1')).toBeDisplayed() 
// Note: One day we could have select API directly on MultiRemoteElement[]

toHave Matchers

// Single element
await expect(multiRemoteBrowser.$('h1')).toHaveText('WebdriverJS Testpage')
await expect(h1).toHaveText({
     'firefox': 'WebdriverJS Testpage',
     'chrome': 'WebdriverJS Testpage'
  })

// Multiple elements
await expect(multiRemoteBrowser.$$('h1')).toHaveText(['Testpage', 'Test CSS Attributes'])
await expect(h1).toHaveText({
    'firefox': ['WebdriverJS Testpage', 'Test CSS Attributes'],
    'chrome': ['WebdriverJS Testpage', 'Test CSS Attributes']
})
await expect(h1.select('firefox')).toHaveText({
    'firefox': ['WebdriverJS Testpage', 'Test CSS Attributes']
})

Error messages

toBe multi-remote single element

Expect multi-remote<chrome, firefox>.$(`h1`) to be displayed

- Expected  - 1
+ Received  + 1

  Object {
    "chrome": "displayed",
-   "firefox": "displayed",
+   "firefox": "not displayed",
  }

toHave multi-remote single elements

Expect multi-remote<chrome, firefox>.$(`h1`) to have text

- Expected  - 1
+ Received  + 1

  Object {
    "chrome": "WebdriverJS Testpage",
-   "firefox": "ebdriverJS Testpage",
+   "firefox": "WebdriverJS Testpage",
  }

toHave multi-remote multiple elements

Expect multi-remote<chrome, firefox>.$$(`h1`) to have text

- Expected  - 2
+ Received  + 2

  Object {
    "chrome": Array [
-     "WebdriverJS Testpage",
-     "Test CSS Attributes",
+     "",
+     "Open Source and Open Governed",
    ],
    "firefox": Array [
      "WebdriverJS Testpage",
      "Test CSS Attributes",
    ],
  }

[dprevost-LMI]

@greptileai, analyze this PR, all the files and the changes, in depth and report any inconsistencies, bugs, or leftover TODOs and incomplete tasks. Ensure you communicate your findings!

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Extends element matchers to support multi-remote browser instances.

The PR appears safe to merge; the remaining documentation inaccuracy is non-blocking.

Findings

1.  Empty arrays do not fail immediately ▶

Summary

This PR adds multi-remote element assertions, per-instance expectations, element-array retry handling, types, tests, and documentation. The latest changes make multi-remote browser .not assertions strict and add tests for that behavior.

_{Reviews (14) · Last reviewed commit: "fix: restore part 2 review fixes lost wh..."}

[dprevost-LMI]

Split the PR into 4 parts for better Greptile reviews. So superseded by

• feat: Multi-remote foundations: types, utilities, element guards and mocks #2228
• feat: Multi-remote browser matchers and expect.multiRemote() #2229
• feat: Multi-remote element matchers ($() and $$()) #2230
• feat: Multi-remote number, size and object matchers and toBeElementsArrayOfSize #2231