nightwatch VS WebdriverIO

Nightwatch which will prompt to create a boilerplate framework specifically for Mobile / TV apps.

6.NightwatchJS: NightwatchJS is a Node.js-based end-to-end testing framework. Key Features: Simplifies writing test scripts using a simple syntax. Supports parallel test execution. Integrates with Selenium WebDriver for cross-browser testing

NightWatchJS

I have shown you the examples of using selectors in the Google Chrome dev tools, but the idea is similar when you write your automation scripts. I will use the Nightwatch testing framework to write the following snippets which will navigate to some webpage, wait to ensure that an interactive element has appeared in the DOM, and finally click on it. If you want to learn using Javascript with Nightwatch framework for your automated tests, you can start with our guide to this.

The reason for this behavior is thoroughly explained in Understanding the Command Queue Nightwatch.js GitHub wiki (it is a long read but it’s worth it). In this section, we will not look in such detail, this is going to be a summary of sorts. By the way, this command queue example can be found in Loadero’s public GitHub examples repository here.

Nightwatch.js is a popular open-source, Selenium JavaScript-based test automation framework for automating browser-based web applications and websites. It is written in Node.js runtime and uses the W3C WebDriver API (formerly Selenium WebDriver) for interacting with various browsers to perform commands and assertions on DOM elements.

For Firefox-specific options (like command-line args and browser about:config prefs), the property to use is moz:firefoxOptions. That is shipping in the latest default nightwatch.conf.js file, as is the parallel goog:chromeOptions for chromedriver. But if you've got a legacy configuration file—like I did—you'll want to update the old chromeOptions property, too.

Github Discussions

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