Canopy VS WebdriverIO

You don't necessarily have to test your JavaScript with JavaScript, btw. Its always good to dabble with other stacks, and it'll add an additional bullet point to your resume. I use a package called Canopy to write very simple tests in F#, which is a Microsoft .NET language.

I've been using canopy for a year now and it rocks. Took a while to port over from C# to F#, but it's a lot more stable than out of the box Selenium: https://lefthandedgoat.github.io/canopy/

3.WebdriverIO: WebdriverIO is another popular open-source test automation framework. Key Features: Integrates well with popular testing frameworks (e.g., Mocha, Jasmine). Supports both synchronous and asynchronous commands. Works with various browsers and platforms

Webdriver.io

There is a tool called webdriver.io which purports to handle mobile automation. I haven't had a chance to play with it yet but it's on my radar.

We recently hired an engineer to write us integration tests with webdriver.io. All of our other tests run fine in Github actions - rspec, javascript jest, etc.

Your automated tests will act on behalf of a real user, open a real web browser (typically Chromium, Chrome, Firefox) using one an existing technology like Webdriver and add some syntactical sugar on top.

WebdriverIO (abbreviated as WDIO) is an E2E testing framework for Node.js. It allows you to automate all kinds of web and mobile applications using the Webdriver or Chrome DevTools protocols.

i recall having to deal with elements inside iframes and shadow roots when using webdriver.io for testing. you can always inspect an element and copy the selector. if it is unique to the page it should work