nightwatch VS react-native-windows

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

Microsoft is using React Native for Windows [0] for their Office applications [1]. As a fan of RN this would be the first avenue I’d explore if I had to develop something for Windows.

[0] https://microsoft.github.io/react-native-windows/

There's also MAUI (.NET) and React Native desktop.

Sometimes yeah they can become a real pain in the a$$. With RN you can make good looking and dynamic layouts with minimum effort. On the other hand when trying to implement logic my main and continuous issues I am facing is with the async parts . Apart from I am all in for RN . I am going to give it a try for a windows app with https://microsoft.github.io/react-native-windows .And if it works fine (which means you get your self away from C#) it will be a really powerful tool for me .

You can read more about it here: https://microsoft.github.io/react-native-windows/

at Microsoft, it's used a lot for brownfield scenarios, similar to react-native-windows: https://github.com/microsoft/react-native-windows

you sound more like a zealot than someone trying to make a point. you can deploy to desktop with react native and have been able to for years now, courtesy of Microsoft: https://microsoft.github.io/react-native-windows/