UI Tests not running successfully

[mmakwanaCertinia]

Summary

When following the readme and upgrading "chromedriver" to "^133.0.2", when you run the UI tests you hit the following error:

TypeError: elements.map is not a function
at async UserContext. (file://ebikes-lwc/force-app/test/utam/page-explorer.spec.js:31:25)

Salesforce Org Type

Scratch Org

Steps To Reproduce

Environment:

Node version: v22.12.0
npm version: 10.9.0
SF version: 2.48.6
chromedriver version: ^133.0.2

Reproduction steps:
Follow the readme and run the UI tests.

Current Behavior

When following the readme and upgrading "chromedriver" to "^133.0.2", when you run the UI tests you hit the following error:

TypeError: elements.map is not a function
at async UserContext. (file://ebikes-lwc/force-app/test/utam/page-explorer.spec.js:31:25)

Expected Behavior

When following the readme and upgrading "chromedriver" to "^133.0.2", when you run the UI tests it passes successfully.

Relevant Log Output

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thank you for posting this issue. 🙇🏼‍♂️
We will come back to you shortly.

[giri-mt]

This seems to be a general problem with UTAM. I have several repos and all have started to fail with same error with Chrome 133. Google doesn't make it easy to stay on older versions of chrome so testing locally is a huge pain.

@pozil where is the appropriate forum to raise this issue ?

[giri-mt]

@mmakwanaCertinia @pozil
Since posting above message, I have now upgraded salesforce-pageobjects package to 8.0 and the issue is gone.
The issue appears to be related to how the newer versions of Chrome interact with the page object model structure - but glad that newer versions have resolved it.

[pozil]

@mmakwanaCertinia, @giri-mt thanks for reporting this.

I've updated the repo dependencies to the latest versions but the issue is still present. It's either a UTAM bug or a base PO issue with the Spring '25 release. I've reported the issue in UTAM JS Recipes as well. I hope that the UTAM team can address it.

[pozil]

Hi all, it took quite some time but I was able to fix the UTAM tests 🎉

It seems that the issue starts to appear when we moved to wdio v9 libs. I failed to isolate the root cause due to some leftover files between my builds.
Knowing this, I was able to upgrade the project to the latest wdio v8 libs and fix my PO definitions (some of the internal LEX page structure has changed).