Inject global variables into main process about karma-electron HOT 3 CLOSED

Can you elaborate on why you need support for this?

from karma-electron.

The navigator contains shared state across multiple pages. Each page builds a navigation menu from data in the navigator and also asks the navigator to change load a different page when a menu linked is clicked.

So it makes sense to me at least that the navigator should be created in the main process so that each page has access to the shared state via remote.getGlobal('navigator')

Thinking out loud:
If I create the navigator on the render process then my page can't get access to it through remote.getGlobal. In other words I would need different way of accessing the variable for testing vs when running the app. I have yet to find a way to do this.

I would also be creating the navigator on the render process which does not reflect how it will be created in the main process when running the app.

from karma-electron.

I don't think karma-electron is best suited for your needs. It's more built for testing single page applications but not how they interact with browser window menus and OS level interactions (e.g. saving application state). The reason is anything application level will wind up being shared by the karma-electron harness which might not properly clear state between test runs.

For browser window menus and OS level interactions, electron has tools like spectron and electron-chromedriver:

https://github.com/electron/spectron

https://github.com/electron/chromedriver

https://github.com/electron/electron/blob/v1.3.6/docs/tutorial/using-selenium-and-webdriver.md

The low level difference between these is:

• karma loads a test harness webpage in electron which opens bootstrapped windows
• electron-chromedriver/spectron controls an electron application via Chromium's wire protocol

from karma-electron.