Looking for Maintainers & Contributors!

[VerteDinde]

Hey folks! We realize many of you use and depend on Spectron for your apps. However, we want to be honest about the current state of Spectron from a maintainer perspective.

Spectron currently has no active maintainers; while we've consistently put out new releases for each new version of Electron, Spectron has had very little maintenance and improvements for over a year.

As we approach Electron 14, Spectron will require a major rewrite in order to continue working without relying on the remote module. This rewrite is currently not planned work, and thus there is unfortunately no guarantee at this time that Spectron will continue working after Electron 14. This, along with a desire to make other improvements, made us decide to put out a call for community help.

We're looking for:

• People who have experience working on Electron-related packages and are interested in becoming a maintainer of Spectron.
• People who maintain their own fork of Spectron and might be interested in improving our upstream (even if you don't want to commit to being a maintainer, help on issues is appreciated)
• People who wouldn't mind jumping in and helping with open issues

If you'd like to help out Spectron, please reach out to me via email (vertedinde@electronjs.org) or reply to this issue.

Thanks all! We appreciate you using Spectron and Electron. 🙇‍♀️

[vladimiry]

For those who are looking for an alternative to spectron I'd recommend exploring https://github.com/microsoft/playwright. I've just switched spectron => playwright and it's been a nicer experience for me so far (btw playwright doesn't depend on the remote module removed in @electron since v14).

[goosewobbler]

I started a rewrite on my fork. Consider it a prototype at this stage, but I got it clicking buttons (with nodeIntegration: false, enableRemoteModule: false, contextIsolation: true)...

https://github.com/goosewobbler/spectron

[goosewobbler]

Rewrite coming along, I updated to WDIO v7 and prototyped a new approach using their testrunner and chromedriver service. Figured Spectron is so heavily tied to WDIO anyway, might as well work with them rather than against them.

[gilles-yvetot]

For those who are looking for an alternative to spectron I'd recommend exploring https://github.com/microsoft/playwright. I've just switched spectron => playwright and it's been a nicer experience for me so far (btw playwright doesn't depend on the remote module removed in @electron since v14).

@vladimiry would you mind sharing your basic setup to run test with playwright. I have seen their gist on their page but it does not work for me

[vladimiry]

@gilles-yvetot I didn't start from the basic setup but just replaced "spectron" with "playwright" keeping the existing structure, and it just worked out from the box (no time-wasting hacking needed as time to time was required for using "spectron"). But I remember that https://playwright.dev/docs/api/class-electron/ and https://playwright.dev/docs/api/class-page pages were helpful. I briefly shared my first experience here. The @avajs is currently used as a test runner in that project but I'm thinking of replacing it with something more simple or maybe with playwright test runner (see here the complete example of using it for @electron case). The test runner is a different topic though, "playwright" itself is supposed to work with any runner.

[gilles-yvetot]

@vladimiry thanks for the help, I could made it work! I agree with you, playwright seems like a very good alternative of spectron!

[cawa-93]

For the future. In one of my projects, I migrated to https://github.com/microsoft/playwright. It was a little harder than I expected. I really missed different examples. I hope my example will be useful to someone:
https://github.com/cawa-93/vite-electron-builder/blob/7d2df55fd8a0b3a803963d62558f719c9034ba2a/tests/app.spec.js

[goosewobbler]

Wasn't able to do anything on my rewrite for a bit. Next step is a WDIO service to handle the ChromeDriver stuff as the CD service I am currently using doesn't allow for restarting. Basically the same approach as before but as a part of the WDIO ecosystem. Don't wait for this, use Playwright in the meantime. I'm only rewriting this because I'm stubborn.