WebdriverIO service for testing Electron applications
Enables cross-platform E2E testing of Electron apps via the extensive WebdriverIO ecosystem.
Spiritual successor to Spectron (RIP).
Makes testing Electron applications much easier via:
- 🚗 auto-setup of required Chromedriver (for Electron v26 and above)
- 📦 automatic path detection of your Electron application
- supports Electron Forge, Electron Builder and unpackaged apps
- 🧩 access Electron APIs within your tests
- 🕵️ mocking of Electron APIs via a Vitest-like API
You will need to install WebdriverIO, instructions can be found here.
The recommended way to get up and running quickly is to use the WDIO configuration wizard.
To get started without using the configuration wizard, you will need to install the service and @wdio/cli:
npm install --dev @wdio/cli wdio-electron-serviceOr use your package manager of choice - pnpm, yarn, etc.
Next, create your WDIO configuration file. If you need some inspiration for this, there is a working configuration in the example directory of this repository, as well as the WDIO configuration reference page.
You will need to add electron to your services array and set an Electron capability, e.g.:
wdio.conf.ts
export const config = {
// ...
services: ['electron'],
capabilities: [
{
browserName: 'electron',
},
],
// ...
};Finally, run some tests using your configuration file.
This will spin up an instance of your app in the same way that WDIO handles browsers such as Chrome or Firefox. The service works with WDIO (parallel) multiremote if you need to run additional instances simultaneously, e.g. multiple instances of your app or different combinations of your app and a Web browser.
If you use Electron Forge or Electron Builder to package your app then the service will automatically attempt to find the path to your bundled Electron application. You can provide a custom path to the binary via custom service capabilities, e.g.:
wdio.conf.ts
export const config = {
// ...
capabilities: [
{
'browserName': 'electron',
'wdio:electronServiceOptions': {
appBinaryPath: './path/to/built/electron/app.exe',
appArgs: ['foo', 'bar=baz'],
},
},
],
// ...
};Alternatively, you can point the service at an unpackaged app by providing the path to the main.js script. Electron will need to be installed in your node_modules. It is recommended to bundle unpackaged apps using a bundler such as Rollup, Parcel, Webpack, etc.
wdio.conf.ts
export const config = {
// ...
capabilities: [
{
'browserName': 'electron',
'wdio:electronServiceOptions': {
appEntryPoint: './path/to/bundled/electron/main.bundle.js',
appArgs: ['foo', 'bar=baz'],
},
},
],
// ...
};If your app uses a version of Electron which is lower than v26 then you will need to manually configure Chromedriver.
This is because WDIO uses Chrome for Testing to download Chromedriver, which only provides Chromedriver versions of v115 or newer.
Service Configuration
Chromedriver Configuration
Accessing Electron APIs
Mocking Electron APIs
Standalone Mode
Development
Common Issues & Debugging
Read the development doc if you are interested in contributing.
Check out our Electron boilerplate project that showcases how to integrate WebdriverIO in an example application. You can also have a look at the Example Apps and E2Es directories in this repository.
If you are having issues running WDIO with the service you should check the documented Common Issues in the first instance, then open a discussion in the main WDIO forum.
The Electron service discussion forum is much less active than the WDIO one, but if the issue you are experiencing is specific to Electron or using the service then you can open a discussion here.