-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests are running slower on the launched chrome browser #262
Comments
Quick thought: could this be related to #217 ?? |
I was having the same issue when using node 14.20x, with node 16.x this does not happen to me.
|
I tried with |
@lferreira07 I'm also on 16.x version of node and still running into the issue. I believe it has something to do with the chromium browser rather than the node version. |
Summary
Tests are running slower on the launched chrome browser
Steps to reproduce
yarn && yarn run test
karma-chrome-launcher
tokarma-firefox-launcher
inpackage.json
. Similarly, inkarma.conf.js
, replacekarma-chrome-launcher
inplugins
withkarma-firefox-launcher
and replacebrowsers
fromChrome
toFirefox
.yarn && yarn run test
. It will launch Firefox now and the tests run way faster than chrome.Description
KarmaJS internally spawns the browser in a child process along with a custom user-data-dir
I observed that on spawned chrome (with a custom user-data-dir), the tests are running very slow as compared to other browsers like Firefox.
I have validated the same by running other test runner such as TestemJS which also spawns the chrome with custom user-data-dir.
In the attached screenshots, you can see that on chrome it is taking around 2 seconds to run the tests where as on Firefox it takes less than 200ms.
I also observed that as more and more tests start running, spawned chrome catches up the speed but falls short (even after catching up) compared to running the tests on non-spawned chrome.
I raised a ticket on the chromium team as well for the same
https://bugs.chromium.org/p/chromium/issues/detail?id=1406168
I'm raising this ticket here as well so that others will be aware of this issue.
Screenshots
The text was updated successfully, but these errors were encountered: