Releases: webdriverio-community/wdio-electron-service
Releases · webdriverio-community/wdio-electron-service
Release 5.1.1
Release 5.1.0
New:
- Support for WDIO config file being in a subdirectory (#206)
- the service will use the nearest package.json file to find a version of Electron
Documentation:
- Inline Electron API documentation when using TS (#220)
- ASAR issues when using Electron Forge (#204)
- Sandbox handling (#204)
- Separate
electron-builder
setup from Electron Forge / other (#204)
Developer:
Release 5.0.0
New:
- WDIO now handles Chromedriver download and process management
- Parallel multiremote supported (WDIO 8.15.0 and up required)
- Service options can now be set in capabilities
- the previous method of setting options still works but capabilities take precedence
- Electron version is inferred from local
package.json
when not specified viabrowserVersion
in capabilities - The
binaryPath
option has been renamedappBinaryPath
- The
appPath
andappName
options (specific toelectron-builder
) have been removed- users of these options should now use the
getBinaryPath
helper inwdio-electron-service/utils
- users of these options should now use the
- Restructured examples
- the app used by the ESM example is now also ESM (since support landed in Electron 28)
- all examples now use Rollup instead of Webpack
- Improved debugging using
debug
- via environment variable: DEBUG='wdio-electron-service'
Fixed:
- Service once again compatible with the latest WDIO (#167)
- Capabilities mapping is now in line with other services
Developer:
- CJS build improvements - now using symlinks
- Script improvements
- Updated dependencies
Release 4.3.0
New:
- The
appArgs
setting is now fully customisable:- This is a result of the service no longer passing through a small set of default args intended to help with the Chromium
DevToolsActivePort
error - Any users wishing to use e.g.
--disable-dev-shm-usage
or any of the other previously default args will need to pass them explicitly inappArgs
- This is a result of the service no longer passing through a small set of default args intended to help with the Chromium
Release 4.2.0
Fixed:
- Browser extensions not exposed correctly when using the service in a CJS project
Developer:
- E2Es now using both ESM & CJS
- E2E test flakiness on CI fixed
- Updated dependencies
Release 4.1.0
New:
- Mock API for mocking Electron main process APIs
- Access to Electron Dialog API
Developer:
- Dependabot enabled on CI
- Updated dependencies
Release 4.0.2
Release 4.0.1
Release 4.0.0
New:
- Substantial rewrite for ESM support
- Chromedriver is now downloaded automatically when service is run without a valid binary path. The Chromedriver version is matched to the Electron version specified in WDIO config.
Fixed:
- Chromedriver process on Windows not cleaned up after specs complete
- Images disabled in test app due to chromeArgs setting
Developer:
- Example repo (https://github.com/goosewobbler/wdio-electron-service-example) moved into this one
- E2Es running locally and on CI
- CI builds running on all platforms
- Jest replaced with Vitest
- Updated dependencies
Release 3.5.1
Fixed:
- Mac Arm64 - Incompatible path with electron builder output
- Type issue in preload spec