Rewrite Discussion
See original GitHub issueI thought I’d put an issue up to discuss my rewrite of Spectron, seeing as forks aren’t allowed their own issues, etc.
Is a rewrite necessary given that Playwright seems to be working well? Possibly not, but I started so I’ll finish. Can’t hurt to have another option, and this approach gives us all the benefits that come with close WDIO integration.
I think the WDIO-first approach works well, though would like to get back to a place where Chromedriver restarts between tests as I don’t think the test state bleed within spec files is expected or desirable. The idea with this is to create a wdio-spectron-service
that is a worker service and can better manage the CD process.
It’s still very much a work in progress but I spent a lot of time documenting things, constructive comments welcome.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:12
Top GitHub Comments
Would be great, looking forward to it… keep up the great work 😃
I’ll close this issue now, added a deprecation notice to my Spectron fork, would appreciate if people could try out the new service and file bugs / feature requests where necessary. Cheers.