Replies: 6 comments 6 replies
-
Hey Peter from 🇩🇰 👋 It seems like you have been using an outdated configuration wizard since we updated the bootstrap process for electron applications in the last release. Can you try again with: npm init wdio@latest ./ Let me know if this works better, thanks! |
Beta Was this translation helpful? Give feedback.
-
Ok, I started using time on getting webdriver working again. My problem right now is that I get the following error: I tried several configurations, see outcommented. But no luck. Any hints sp solve these errors occuring is much appreciated. Config:
|
Beta Was this translation helpful? Give feedback.
-
For some reason it seems to fail downloading the chrome for testing driver, but the path seems very odd to me: "https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/114.0.5735.133/mac-x64/chromedriver-mac-x64.zip". I ran the pure project as explained in the video, and this project works fully. I'm going to compare the package.json files to see what is different between the two solutions. |
Beta Was this translation helpful? Give feedback.
-
Upgraded to electron 27.0.1 and now it seems to find the correct driver, and now after a npm package, at last it can run the basic test:-) I'm very happy. Now to writing some great test. |
Beta Was this translation helpful? Give feedback.
-
OK, not so happy after all:-( Now i started looking at running some test, I discovered that the application/chromium starts but the React GUI is never loaded. Putting in a pause on the browser, I just see a blank page with no html elements. I see the correct Electron menu, but it is running the App in prod release, so I cant access the dev tools. |
Beta Was this translation helpful? Give feedback.
-
Please Help me I follwed - and I write a test as mentioned in doc
But it throw type-script error Property 'electron' does not exist on type 'Browser'. |
Beta Was this translation helpful? Give feedback.
-
I'm completly new to webdriver/electron testing. I'm following the guide from https://webdriver.io/docs/desktop-testing/electron/.
I'm on OSX, node v18.17.1, Electron v25.0.1 npm v9.6.7
Here's the experience:
Create a new empty dir for the test project (Maybe it needs to be added to the App project instead?)
Run rpm create wdio@latest ./
Select “Desktop Testing - of Electron Application
Set path to: /Users/mac20rd01/Source/DPA Audio Controller Test/DPA%20Audio%20Controller/release/app/dist (Notice, this is not the path to a binary but to output from a build)
Select Mocha
Select Typescript compiler
Select generate test files
Select default location
Select spec and Allure
Select no plugins
Select to add electron as a service to test setup
Run npm install
Do npm run wdio
I get:
Ok so I add missing definition to the package.json file. Guess it expected the test project to be hacked into the App project or?
Run npm run wdio again this time getting:
Ok what is wrong here. I thought that adding the 'electron' service should setup capabilities. It says so in the conf. file:
Then I've hacked around adding capabilities anyway, like:
I get to a place where the app starts, I see the correct menus but renderer is blank, does not seem to load/run renderer scripts.
And I get more errors in console. The app hangs, no test output:
Can anyone with some decent experience please help me getting it up and running, thanks
Best regards, Peter from Denmark
Beta Was this translation helpful? Give feedback.
All reactions