electron-settings VS WebdriverIO

Use electron-settings (no updates in 2 years)

electron-settings https://github.com/nathanbuchar/electron-settings

One relatively straightforward way to do that would be to use something like electron-settings to record a little bit of persistent state data to disk. I.e., in your main.js as part of the app bootstrapping logic you would (1) attempt to read a "first_launch" flag from the settings, and (2) when missing, post the info to the server and write the first_launch=true flag to the settings so you know you've done it already on the next launch.

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