Comments (4)
This is expected behavior. When we shut off useIframe
, Karma moves to using window.open
instead so there are 2 windows:
- Karma's test harness (communicates to Node.js, starts new test runs)
- Karma's test runner (loads testing framework/test files, communicates success/fail information to test harness via
window.parent
)
To demonstrate this point further, we could disable useIframe
in other browsers and see the same result (e.g. Chrome, Firefox)
from karma-electron.
The thing is that without useIframe: false
we lose nodeIntegration
, but with it, it shows 2 windows, with the second being incredibly annoying poping up all the time.
I guess the idea is to run with --show
flag off and only show when we need to debug the tests, right?
from karma-electron.
Yep, typically showing the window isn't too helpful as content is often added/remove quicker than we can see. To make it less painful to add/remove the --show
flag in karma.conf.js
, I use the following setup:
Add ElectronVisible
browser but don't set it as default browser:
browsers: ['Electron'],
customLaunchers: {
ElectronVisible: {
base: 'Electron',
flags: ['--show']
}
}
Override default browsers via CLI:
karma start --browsers ElectronVisible
# or for `npm-scripts`
npm run test-karma -- --browsers ElectronVisible
from karma-electron.
Nice
from karma-electron.
Related Issues (20)
- How to use with karma-babel? HOT 27
- `electron` did show not nothing happen then HOT 1
- Can't import nodejs modules in an angular-cli project (Typescript) HOT 1
- Errors without stack traces coming from karma-electron? HOT 5
- running with ndb for debugging? HOT 2
- Unable to open Electron window using --show HOT 3
- Electron 5 nodeIntegration HOT 12
- Custom launcher `require` mechanism doesn't work HOT 4
- Module paths are messed up HOT 5
- Error: Karma plugin is meant to be used from within Angular CLI and will not work correctly outside of it HOT 1
- How to configure NODE_PATH for the Electron instance? HOT 24
- [feature] option like 'require', but for renderer processes. HOT 1
- Karma times out when using Electron 9 and client.useIframe = false HOT 20
- Non-context aware native modules in renderer will cause specs to error HOT 3
- [questions] Is Electron 12 supported? HOT 16
- electron V12.0.4---------require is not defined HOT 3
- ES Modules HOT 2
- "require is not defined" after update to karma-electron 7 / electron 12 HOT 12
- Regardless of the `browserWindowOptions.show` value, a window always opens. HOT 12
- sqlite3 stalls with nodeIntegration true contextIsolation false HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from karma-electron.